[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#542865: Grant an FHS exception for the multiarch library directories



Manoj Srivastava <srivasta@debian.org> writes:

> On Fri, Aug 21 2009, Russ Allbery wrote:
>
>> Steve Langasek <vorlon@debian.org> writes:
>>> On Fri, Aug 21, 2009 at 03:47:24PM -0700, Russ Allbery wrote:
>>
>>>> It looks good to me as a first step.  Seconded, with the caveat that we
>>>> probably don't want to release this with Policy until we've hammered
>>>> out any specific restrictions on how those directories can be used
>>>> first.
>>
>>> I think the only specific restriction needed is already spelled out -
>>> that packages can only install to the triplet matching their own
>>> architecture.  Are there other restrictions that you think are called
>>> for?
>>
>> The current restriction is specific to libraries.  Don't we need to say
>> that you can't put *any* files into any triplet directory that isn't for
>> your package architecture?
>
>         Hmm. My first read was that one could not put anything that was
>  not a library in these directories, but perhaps it should be stated
>  explicitly.
>
>         manoj

That isn't the case for /usr/lib/package. Pretty much anything can be
in there.

Under multiarch that would be /usr/lib/tripplet/package/. I believe
that needs to be spelled out as that is the sane place to put plugins,
anything dlopened or data that is architecture sensitive.

The alternative would be to recommend packages use
/usr/lib/package/tripplet/, which I feel breaks consistency with the
use of /usr/include/triplet/[package/], /lib/triplet/ and
/usr/lib/triplet/.

MfG
        Goswin


Reply to: