Re: Detecting shishi from autoconf

[Simon Josefsson]

Elrond <address@hidden> writes:

> On Tue, May 16, 2006 at 01:04:18PM +0200, Simon Josefsson wrote:
> [...]
>> > I know, it's not your fault, just wanted to let someone
>> > know about the traps available.
>> 
>> Yup, readline is a problematic library to link to properly,
>
> It was an example of optional dependencies. shishi has the
> same optional dependencies issue.

But shishi uses libtool, so if you are using libtool to link your
application, it will handle the dependencies internally.

> My problems with it currently:
>
> - Getting one thing from it, gets you the whole load of it.
>
>     readline -> getline -> getdelim
>
>   While I'm happy, when readline is not there, I don't need
>   emulation for it.

Hm, it should be possibly to write a module readline-opt that doesn't
implement a fallback, and have the readline module use it, but install
it's replacement when needed.

> - I still haven't moved to automake (aclocal a few days
>   ago at least) for historic reasons. Which means
>   hand-adding all the cruft (cruft I haven't asked for in
>   the first place)

Oh.  Gnulib pretty much assume all the autotools machinery.  Only
libtool is optional, I think.

> - There's so much stuff in gnulib (and autoconf-archive),
>   that *could* be useful to replace _working_ code, there's
>   just too much of it. ;)

Yup.

/Simon