bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Sync maintainer-makefile files


From: Micah Cowan
Subject: Re: Sync maintainer-makefile files
Date: Mon, 22 Oct 2007 11:50:18 -0700
User-agent: Thunderbird 1.5.0.13 (X11/20070824)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Simon Josefsson wrote:
> Micah Cowan <address@hidden> writes:
> 
>>> The second set of patches is against gnulib to remove most of the rules
>>> in coreutils, to avoid duplication.  This removes some features from
>>> gnulib's maint.mk, but has anyone been using them heavily?  If so, we
>>> can add them again by making small incremental patches against coreutils
>>> and gnulib.
>>>
>>> Thoughts?
>> Didn't you just remove the vast majority of targets from maint.mk?
>> There's barely anything left at all! Why bother having a maint.mk in the
>> first place then?
> 
> It isn't completely empty, and more importantly, it serves as a place
> holder for things to move from coreutils.

Is coreutils' maint.mk essentially a superset of gnulib's, then?

>> I have only just begun using it, but I find all of the following useful:
>>
>>> -sc_cast_of_argument_to_free:
>>> -sc_cast_of_x_alloc_return_value:
>>> -sc_cast_of_alloca_return_value:
>>> -sc_space_tab:
>> ^^  *especially* that one...
>>
>>> -sc_changelog:
>>> -syntax-check: $(syntax-check-rules)
>> Throwing out several useful rules, which AFAICT make up almost the
>> entirety of maint.mk, just because coreutils already has them, is a bad
>> move, IMO.
> 
> Once we have made coreutils use the gnulib module for these files, would
> you be interested in working on merging back the rules from coreutils to
> gnulib?  You could propose patches for both coreutils and gnulib.  Many
> of the rules will need to be thought through because coreutils have
> several assumptions that doesn't hold in gnulib.

Perhaps; but it's not clear to me why it's necessary to delete the
existing rules from gnulib in order to migrate them from coreutils.
Can't we just migrate any changes to them one by one?

Since the Gnulib usage model involves grabbing the latest via Git or
CVS, I would expect Gnulib's repos to be in a pretty stable point at any
particular point in time. If you apply the proposed patch, then anyone
who does a pull and a gnulib-tool --update may be surprised to find
their favorite maint.mk rules suddenly vanish, until such time they are
reinstated from coreutils.

May I suggest that, if it is really most convenient to do it this way,
the mainline repo be cloned to a special-purpose one to work on this, so
that the mainline itself may retain full functionality, and that
coreutils use that one during migration to gnulib's maintainer-makefile?

- --
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer...
http://micah.cowan.name/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHHPDp7M8hyUobTrERCFciAJ9my+lgzcduIIlBo8lz9C0HEW5IKgCdF9u8
UvyuDLbNw7wM3AYPrv3Ks50=
=ntl1
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]