On Wed, Apr 02, 2003 at 04:49:41PM +0200, Thomas Viehmann wrote:
> Is it advisable for such .so's that are not intended to be linked
> against to go into /usr/lib, or is it preferable to have them in
> /usr/lib/package?
IMHO a loadable module that is used by a program with dl*() has nothing
to do
On Wed, Apr 02, 2003 at 04:49:41PM +0200, Thomas Viehmann wrote:
> Is it advisable for such .so's that are not intended to be linked
> against to go into /usr/lib, or is it preferable to have them in
> /usr/lib/package?
IMHO a loadable module that is used by a program with dl*() has nothing
to do
Hi,
On Wed, 02 Apr 2003 14:49:41 +, Thomas Viehmann wrote:
>
> Is it advisable for such .so's that are not intended to be linked against to
> go
> into /usr/lib, or is it preferable to have them in /usr/lib/package?
> (Just curious.)
>
IMHO, if there's more that would go into /usr/lib/packa
Hi,
On Wed, 02 Apr 2003 14:49:41 +, Thomas Viehmann wrote:
>
> Is it advisable for such .so's that are not intended to be linked against to go
> into /usr/lib, or is it preferable to have them in /usr/lib/package?
> (Just curious.)
>
IMHO, if there's more that would go into /usr/lib/package,
Jamie Wilkinson wrote:
> There is nothing wrong with a program and a shared library that it uses
> being in the same package, given that the shared library is of no interest
> to any other program on the system.
>>My inclination is to include a lintian override and to package it as
>>is. The libra
This one time, at band camp, martin f krafft wrote:
>i don't really know what to do in this case. Rex Tsai wants to
>package proxychains. The package contains libproxychains.so, but
>ther are no SHLIBS. i told him that instead, he should package
>libproxychains separately, and make the proxychains
Jamie Wilkinson wrote:
> There is nothing wrong with a program and a shared library that it uses
> being in the same package, given that the shared library is of no interest
> to any other program on the system.
>>My inclination is to include a lintian override and to package it as
>>is. The libra
This one time, at band camp, martin f krafft wrote:
>i don't really know what to do in this case. Rex Tsai wants to
>package proxychains. The package contains libproxychains.so, but
>ther are no SHLIBS. i told him that instead, he should package
>libproxychains separately, and make the proxychains
doods,
i don't really know what to do in this case. Rex Tsai wants to
package proxychains. The package contains libproxychains.so, but
ther are no SHLIBS. i told him that instead, he should package
libproxychains separately, and make the proxychains package depend
on that. To that, he writes:
> T
doods,
i don't really know what to do in this case. Rex Tsai wants to
package proxychains. The package contains libproxychains.so, but
ther are no SHLIBS. i told him that instead, he should package
libproxychains separately, and make the proxychains package depend
on that. To that, he writes:
> T
10 matches
Mail list logo
