Re: module libposix

[Bruce Korb]

Hi Bruno,

On Sat, Sep 18, 2010 at 4:12 PM, Bruno Haible <address@hidden> wrote:
>> My suggestion would be to consider any recommended action that triggers a 
>> "this
>> is obsolete" message to be a bug.  The fix might belong in the docs, it 
>> might belong
>> in not construing something obsolete or it might be to internally suppress 
>> the
>> warning.  Wherever the fix belongs, it is unlikely that the person stubbing 
>> their toe
>> on it is going to have a best guess as to where it belongs.
>
> OK, it sounds you're undecided. My opinion is that the 'posix-modules' script,
> like 'gnulib-tool', should ignore obsolete modules by default, and have an
> option --with-obsolete.

I'm not undecided.  It should be a bug to get such messages when using
'posix-modules'
or when using non-obsolete modules.  How the bug should be addressed is
a different question and will depend on the particulars.

> Good. Additionally you should also include the version number as determined by
> 'git':
>   ./build-aux/git-version-gen /dev/null | sed -e 's/-dirty/-modified/'

"UNKNOWN-modified"?  I don't know how you'd want to see that worked
into a version number.

>> 2.  replacing libgnu.a with libposix.la
>
> You can use the gnulib-tool option --lib=libposix for this purpose.

Ah.  OK.  Next time I've got play time for this.

>> 5. removing libtool conditionality -- making it required
>
> I don't see where you pass the option --libtool to gnulib-tool.
>
>> I'm not done yet, so there may be more.  I'm doing it all with a single file 
>> --
>> a shell script that does everything.
>
> I note that your script requires bash-4.x (I get a syntax error with 
> bash-3.2.39)
> and libtool-2.x in the PATH (I get an automake error "required file
> `build-aux/ltmain.sh' not found" otherwise).

The purpose of the script is to generate an installable project named
"libposix".
It, itself, does not need to run on all platforms.  The generated project does.
First, I get it working, then I'll fiddle the script to be more widely runable.

>> It presumes itself to be living in a subdirectory within gnulib.
>
> It works also anywhere, assuming that gnulib-tool can be found in PATH.

Yes, but that is not generally true unless you specifically put the
gnulib directory
into your path.  Surely, I'll polish it some.  First, I need to get it
working at all.

Cheers - Bruce