Re: Upcoming Debian multiarch support (amd64, sparc64, s390x, mips64) [affects sarge slightly]
* Goswin von Brederlow
| > /etc/* -> /etc64/*
| > (config files may be architecture specific)
|
| Hardly irregular for libs to have conffig files. Any example?
PAM, though that's not arch-specific.
| > */include/* -> */include64/*
| > (header files may be architecture specific)
|
| Use #ifdef __AMD64__ #elif __I386__ ....
eww. This will be especially fun for asm/ and bits/
| Contents of packages and name of packages are two seperate
| problems. We are aware of the further problems with the contents and
| splitting out common files into binary-all packages even more
| aggresively than its already done seems to be the only way to go for
| the contents.
It'll mean we'll get a zillion libfoo-dev-common packages, I think.
--
Tollef Fog Heen ,''`.
UNIX is user friendly, it's just picky about who its friends are : :' :
`. `'
`-
Reply to:
- References:
- Upcoming Debian multiarch support (amd64, sparc64, s390x, mips64) [affects sarge slightly]
- From: Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>
- Re: Upcoming Debian multiarch support (amd64, sparc64, s390x, mips64) [affects sarge slightly]
- From: Anthony Towns <aj@azure.humbug.org.au>
- Re: Upcoming Debian multiarch support (amd64, sparc64, s390x, mips64) [affects sarge slightly]
- From: Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>
- Re: Upcoming Debian multiarch support (amd64, sparc64, s390x, mips64) [affects sarge slightly]
- From: Scott James Remnant <scott@netsplit.com>
- Re: Upcoming Debian multiarch support (amd64, sparc64, s390x, mips64) [affects sarge slightly]
- From: Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>