-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to David Lutterkort on 6/2/2008 10:52 AM: | On Mon, 2008-06-02 at 14:00 +0200, Jim Meyering wrote: |> If I hear no objection soon, I will sync gnulib's argz.c |> directly from glibc, using something like the above. |> Then, gnulib and libtool can evolve separately, if needed. |> |> However, I'd really like to hear that at least one owner of |> an one argz-using project agrees with this approach. | | Since I started this whole discussion: I am perfectly fine with this | approach.
Libtool doesn't need all of the argz functions, but I can see the value in gnulib offering them all. In that case, it's nicer to modularize things (provide each argz function as its own module, so that you don't drag in the functions you don't use) rather than have a single argz.c (or maybe still share a single argz.c, but with the various functions protected by HAVE_GNULIB_ARGZ_* as selected by various module indicators). What would the libtool folks think of a patch to make libtool start depending on gnulib, and make gnulib the master repository for the argz replacements? I'm not convinced that diverging libtool and gnulib is the best route yet, but I'm also not sure that libtool wants to drag in everything argz related. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkhElEUACgkQ84KuGfSFAYCJ/wCeLx1zy3OSFGsDeRwSmCE786Nq eHoAoJZ4gEqrwy6PMQMrkMNXoNGo9tFM =DmLq -----END PGP SIGNATURE-----
