On 10/12/10 13:43, Bruno Haible wrote:
> Hi Gary,
>
>> Making libposix into a module makes life considerably easier.
>
> Yes, it triggers the magic that tells gnulib-tool to omit the augmentation of
> noinst_LIBRARIES.
>
> But I don't agree with putting the module list here. Who will keep it
> up-to-date? The maintainable solution is to use `./posix-modules`. But how?
> Either
> a) extend gnulib-tool so that it understands
> Depends-on:
> `./posix-modules`
> and invokes the 'posix-modules' script.
> Or
> b) Invoke ../posix-modules in the bootstrap script of the 'libposix'
> subdirectory.
Or:
c) create a script that auto-replaces the Depends-on: section of
the module/libposix file?
Thus, it has the advantage of gnulib-tool magic and it avoids
the maintenance hassle. The bootstrap script *could* just run it.
For that matter, we have a "d":
d) libposix gets added to modules/.gitignore and libposix/bootstrap
generates it before invoking gnulib-tool ? :-D
How's "d"?
