Re: multiarch status update
Gabor Gombas <firstname.lastname@example.org> writes:
> On Wed, May 17, 2006 at 12:14:24AM +0200, Goswin von Brederlow wrote:
>> Multiarch (so far) does not allow the same path/file in 2 packages
>> (with the exception of /usr/share/doc/ files)
> Hmm. How do you want to handle one-arch-only binNMUs? binNMUs change
> changelog.Debian.gz, so
> - you can't upgrade just the architecture that was binNMUed without
> changelog.Debian.gz becoming invalid for the other arches
> - there will be no new version for the other arches so you can't just
> wait till the versions are in sync
Afaik nothing in the package may depend on the existance of
/usr/share/doc so it doesn't realy matter (to the package) what
happens there. Handling the special overlap for changelog and readme
files there can be implemented in several ways:
1) Don't care about it
Just assume --force-overwrite for anything in /usr/share/doc.
Whatever gets installed last sticks and removal of packages can
lead to files getting removed and so on.
A slightly better thing would be to always keep the highest version
as that should include prior versions info as well.
2) Automaticaly divert
This has the small problem of not workign with 3 or more archs
since dpkg only handles one diversion.
3) Automaticaly append the arch tripplet to the files
4) Don't allow it
Split those files off into architecture:all packages. For packages
that have one anyway this is probably the sanest thing. But
creating a package with just the changelog, copyright and readme is
kind of insane.