Re: Documentation of lib$package.a?

[Simon Josefsson]

Reuben Thomas <address@hidden> writes:

>> Similarly there is no code in bootstrap rewrite to override the default
>>> setting of --lib, save setting gnulib_name=lib$package in bootstrap.conf.
>>> Bootstrap rewrite is extremely configurable, so maybe you are overwriting
>>> setting gnulib_name somehow from bootstrap.conf?
>>>
>>
>> Nope, it's the default, commit a1c6bc99 by Jim Meyering back in 2007:
>>
>> gnulib_name=lib$package
>>
>>
>> That seems entirely wrong to me.  If I have a package, say GNU m4, then
>> libm4 is a library built and installed by my package. Why on earth would I
>> want gnulib to stomp all over my namespace?  At least there is a straight
>> forward work around:  In your gnulib bootstrap using package, always set:
>>
>>   gnulib_name=libgnu
>>
>
> Any comments from other maintainers?

Personally I have found that bootstrap is not applicable to projects
that ships libraries and have command line tools for the library.  There
are multiple reasons for this, the above issue seems to another example.

/Simon