Re: -= PROPOSAL =- Release sarge with amd64
Raul Miller <moth@debian.org> writes:
>> On Sun, Jul 18, 2004 at 08:15:18AM -0400, Raul Miller wrote:
>> > [2] build packages to take advantage of this:
>> >
>> > [*] make important shared libs biarch
>> > [*] list amd64 packages which don't export shared library
>> > interfaces as supporting all architectures.
>> > [*] introduce dependencies between important packages, reflecting
>> > the needs of an install onto i386.
>> >
>> > The straightforward approach to doing this and complying with LSB means
>> > it would probably be a good idea to supress glibc warnings about both
>> > kinds of libs in /lib and /usr/lib/. So patch gcc to not issue that
>> > warning if a specially named file is in a lib dir, and the archtectures
>> > present are those listed in that specially named file.
>
> On Sun, Jul 18, 2004 at 02:35:58PM +0200, Kurt Roeckx wrote:
>> Where do you plan to install those 2 libs with the same name?
>
> 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.
And what do you do with files that are in both packages?
Ups, you need to split the lib into arch and common files (which you
can't for sarge).
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.
And and and ...
And then when you have something working you implemented multiarch and
are one year down the road.
MfG
Goswin
Reply to: