>> You should consider /usr/lib// if you want to make your
>> package multiarch-safe.
>
> And what about ?
>
> /usr/lib//
>
> whcih one is better ?
Have a look at the Debian policy at
https://www.debian.org/doc/debian-policy/ch-opersys.html#s-fhs
It explicitly mentions:
> Applications may also
> so my question is how can I solve this error.
> I thought about adding rpath to these libraries in order to move then
> under a private location /usr/lib/. But for this I need to add
> an rpath to all the extensions which use these libraries.
You should consider /usr/lib// if you want to make y
On Sun, Apr 12, 2020 at 03:18:39PM +0200, picca wrote:
> I thought about adding rpath to these libraries in order to move then
> under a private location /usr/lib/.
This looks like the correct way to solve this.
> The issue is that the current build system do not provide rpath for
> these librar
Hello, I am working on the dials[1] package. This scientific software
produce a bunch of python extension via boost python, but also a bunch
of libraries, which are the common part of the python extension.
when I package it, I moved the common library under the /usr/lib//
directory. This way the
4 matches
Mail list logo