RE: amd64 and dpkg and so
"One more important problem is that that attempt would
prevent us from getting a clean upgrade path to the
correct solution."
Well... maybe. Is there any way that both 64-bit and 32-bit versions of Debian could be installed on the same system, each unaware of the other and believing that they're in their own little world? There must be some way around 32-bit and 64-bit versions of the same package creating conflicts.
-----Original Message-----
From: Arnd Bergmann [mailto:arnd@arndb.de]
Sent: Friday, August 29, 2003 2:43 PM
To: debian-x86-64@lists.debian.org
Subject: Re: amd64 and dpkg and so
On Friday 29 August 2003 23:25, Ron Johnson wrote:
> Pardon my ignorance, but what does that mean?
There are packages that rely on libraries being in /usr/lib.
They obviously need to be changed to find them in /usr/lib64
when running on a biarch 32/64 bit system. E.g. KDE has been
changed to default to a $prefix/lib64 path when running on
amd64, which is the correct thing to do (according to LSB).
It would be just wrong to patch upstream packages into
non-standard behavior in order to get a short-term solution.
One more important problem is that that attempt would
prevent us from getting a clean upgrade path to the
correct solution. Right now we have a (potential) way of
upgrading i386 to amd64, once we start getting incompatible
with the rest of the world that won't work anymore.
Arnd <><
--
To UNSUBSCRIBE, email to debian-x86-64-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: