Re: Multiarch file overlap summary and proposal
- To: Josselin Mouette <joss@debian.org>
- Cc: Russ Allbery <rra@debian.org>, debian-devel@lists.debian.org, debian-dpkg@lists.debian.org
- Subject: Re: Multiarch file overlap summary and proposal
- From: Goswin von Brederlow <goswin-v-b@web.de>
- Date: Thu, 23 Feb 2012 15:00:33 +0100
- Message-id: <874nuhzm2m.fsf@frosties.localnet>
- In-reply-to: <1329230441.3297.378.camel@pi0307572> (Josselin Mouette's message of "Tue, 14 Feb 2012 15:40:41 +0100")
- References: <20120206073115.GB2033@rivendell.home.ouaza.com> <20120207095921.d5142d88cbb3dca679f33ec9@debian.org> <20120210225620.GA8782@gaara.hadrons.org> <20120211001446.GB2797@jwilk.net> <20120211005559.GA32671@burratino> <20120211011629.GB20155@virgil.dodds.net> <87zkcqrw2w.fsf@windlord.stanford.edu> <20120211185237.GA10129@virgil.dodds.net> <874nutncef.fsf_-_@windlord.stanford.edu> <1329230441.3297.378.camel@pi0307572>
Josselin Mouette <joss@debian.org> writes:
> Le lundi 13 février 2012 à 22:43 -0800, Russ Allbery a écrit :
>> There's been a lot of discussion of this, but it seems to have been fairly
>> inconclusive. We need to decide what we're doing, if anything, for wheezy
>> fairly soon, so I think we need to try to drive this discussion to some
>> concrete conclusions.
>
> Thank you very much for your constructive work.
>
>> 3. Generated documentation. Here's where I think refcounting starts
>> failing.
>
> So we need to move a lot of documentation generated with gtk-doc or
> doxygen from -dev packages to -doc packages. But it really seems an
> acceptable tradeoff between the amount of work required and the
> cleanness of the solution.
>
>> Does this seem comprehensive to everyone? Am I missing any cases?
>
> Are there any cases of configuration files in /etc that vary across
> architectures? Think of stuff like ld.so.conf, where some plugins or
> library path is coded in a configuration file.
Generally conffiles in library packages is a violation of policy
8.2. They would create a file overwrite conflict if the SONAME
changes. Putting the conffile into the -common package is a good
solution.
There are some exceptions where the conffiles are version qualified.
E.g.: libgtk2.0-0: /etc/gtk-2.0/im-multipress.conf
For conffiles that vary across architectures the path or name must
include the multiarch triplet.
E.g: libc6: /etc/ld.so.conf.d/x86_64-linux-gnu.conf
(Note: this is actualy a violation of policy 8.2 and needs to be fixed
when we get a libc7).
MfG
Goswin
Reply to: