Michael Piefel <[EMAIL PROTECTED]> writes:
> Am Donnerstag, den 13.10.2005, 09:32 +0200 schrieb Goswin Brederlow:
>> the libmagic1 package contains magic files in /usr/share/misc/file
>> that will cause a future libmagic2 to conflict with libmagic1
>> preventing a clean transition.
>
> How do you know what the files will be called in libmagic2?
I'm assuming you won't rename the files (and rewrite the file source)
just because the libmagic ABI changes, e.g. due to an incompatible gcc
update like m68k/hppa is going through now.
>> This also prevents clean multiarch
>> packages from working.
>
> I donât understand.
For multiarch it might be neccessary to install both a 32bit libmagic
and 64bit libmagic. The library files reside in different subdirs so
they don't conflict but any files outside /usr/lib/ will clash.
>> Please split the architecture independent data files out of the
>> library package to facilitate future compatibility.
>
> How will that help? How will a split prevent the file name clash?
Assuming the binary format of /usr/share/misc/file doesn't change both
libmagic1 and libmagic2 would depend on libmagic-common (or
file-common). Either the old or new version would suffice. Same for
libmagic1:i386 and libmagic1:amd64 for multiarch, both would use the
same common file.
> Bye,
> Mike
MfG
Goswin
