Re: [SCM] GNU Libtool branch, master, updated. v2.2.7b-4-gaa75582

[Ralf Wildenhues]

Hi Gary,

* Gary V. Vaughan wrote on Fri, Jun 04, 2010 at 07:50:31PM CEST:
>     Provide an m4sh reimplementation of announce-gen.
>     
>     * libltdl/config/getopt.m4sh (M4SH_GETOPTS): New macro that takes
>     a quoted m4 list of command line options to be parsed, and
>     generates the shell code to parse those options and collect the
>     results into appropriately named 'opt_xxx' shell variables.  Also,
>     add some private supporting macros, and improve the comments
>     radically.
>     * libltdl/config/announce-gen.m4sh: New file, to generate and
>     optionally post (an enhancement over the gnulib perl script of the
>     same name) a release announcement.
>     * Makefile.maint (announce-gen): Build a new announce-gen script
>     in the build directory, from the contents of
>     libltdl/config/announce-gen.m4sh.
>     * HACKING (Release Procedure): Update the instructions to use
>     announce-gen.
>     (Alpha release note template, Full release note template):
>     Removed.

I see the point in the factorization of the option parsing, and I have
to admit to not having tested or even looked in detail at these changes
yet, but on a general note, shouldn't we either just use gnulib's
announce-gen if it is good enough for us?  And if it isn't, shouldn't we
try to get the improvements of your version into gnulib's, or even try
to get gnulib to adopt the libtool variant?

I realize my reaction to an earlier suggestion of yours about this was a
bit inconsistent with this statement now, sorry about that.  A bit more
general, how come things like clcommit, mailnotify, and announge-gen
live in the Libtool package?  They are not very specific to library
handling.

What do you think?  And yes, I don't mind leaving things as they are,
this is just an observation.  I realize you've just invested quite a bit
of work on this.

Cheers, and thanks,
Ralf