Re: [softwerk-dev] new release, plus "manual": SUCCESS!

[Paul Barton-D. <pb...@op...>]

>Okay, that makes more sense. When I get a lib that I don't want to
>install system wide I usually install it in like ~/lib and add that to my
>LD_LIBRARY_PATH. I can see that its a mess though, because configure
>would still need to know the location of it to test if its there. 

No, it doesn't. If a library exists in such a way that ld(1) can find
it, then configure will find it too (because it uses ld(1) to do so).

This doesn't apply to the non-library components of a package, and
this is how the "*-config --[libs|cflags]" convention has come into
being.

In the case of my tarball releases, what you build is intended to be
entirely local to the application and not for reuse by anything
else. if you don't like that, then use the CVS repositories, and do a
global install of the libraries. it will work either way.

--p