Re: Request for Help: Attal
2008/2/11, Barry deFreese <email@example.com>:
> Because they aren't used by other packages. I can't keep up with this
> because I keep getting different answers. If I have a lib in /usr/lib,
> isn't it also policy that I have to have a lib binary package?
> I guess I would call them shared private libs or something? I suppose I
> could build it with static libs but the way it's packaged, I think I
> might still have the same problems.
You can have a look at this thread . In Vorlon's words : "if
they are not for public consumption, they should be kept in their own
subdirectory and a mechanism such as rpath, LD_LIBRARY_PATH in a
wrapper script, or dlopen()ing used instead."