On Mon, 09 May 2011, sean finney wrote: > On Sun, May 08, 2011 at 09:05:20PM +0200, Raphael Hertzog wrote: > > The control files are installed as <pkg>.foo except for Multi-Arch: same > > which are installed as <pkg>:<arch>.foo. > > > > It's probably a good idea to reuse the same logic here. > > If a package migrates from non-multiarch to multi-arch, that means > that the location of the conffiledb for the package would change, right?
Right. > If so, then I think we'd need to either ensure that the implementation > can support it[1], or just be lazy and always have the arch[2]. > > [1] checking the multi-arch status of the package's previous version to > determine the conffiledb path at appropriate points in the code, > assuming that can be done. I have not looked into details but I don't see why this couldn't be done. BTW, always using the arch has other problems: cross-grading a multi-arch foreign package from one arch to the other would need special care too. And switching from arch all to arch any would also cause problems. > [2] assuming i read the spec correctly you can't have two copies of an > arch:all package installed. That's true. Cheers, -- Raphaël Hertzog ◈ Debian Developer Follow my Debian News ▶ http://RaphaelHertzog.com (English) ▶ http://RaphaelHertzog.fr (Français) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
