Re: -= PROPOSAL =- Release sarge with amd64
Raul Miller <moth@debian.org> writes:
>> > For packages which provide both, the amd64 instance goes in /lib64 and
>> > the i386 instance goes in /lib
>> >
>> > For other packages (any where there's an explicit IA32 package), the
>> > current system is fine.
>
> On Sun, Jul 18, 2004 at 04:36:46PM +0200, Goswin von Brederlow wrote:
>> And what do you do with files that are in both packages?
>
> For the each base package which provide shared libs, you've got just
> one deb which supports two architectures. Other packages can keep
> their current organization (unless there's some real great reason to
> put together a package which supports both architectures, but almost
> nothing outside base should need this).
Ok, that is the bload every lib to twice its size way.
> If that doesn't address your concern, could you be more specific?
>
>> Ups, you need to split the lib into arch and common files (which you
>> can't for sarge).
>
> Why do you need to split these?
Doesn't apply when having just one deb.
>> And then you get a problem with the -dev package. Because you need two
>> of them. So now you need /usr/include and /usr/include64.
>
> Why do you need two of these?
>
> You've got one binary package, why do you need two -dev packages to
> produce one binary package?
You need the 32bit and 64bit include files. One or two packags doesn't
realy matter.
For libc6 and linux-kernel-header you can probably create a package
with both merged by adding lots of #ifdef to the files. It sure
would be ugly. And again double the size.
(Ok libc6 has biarch support already, bad example. s/libc6/libfoo/g).
MfG
Goswin
Reply to: