Package: dpkg-dev
Version: 1.10.27
Severity: wishlist
File: /usr/bin/dpkg-architecture

Hi,

I would like for dpkg-architecture to include 3 more variables:

For single arch systems:
DEB_HOST_LIBDIR   = lib

For native 32bit biarch systems:
DEB_HOST_LIBDIR   = lib
DEB_HOST_LIB32DIR = lib
DEB_HOST_LIB64DIR = lib64

For native 64bit biarch systems:
DEB_HOST_LIBDIR   = lib
DEB_HOST_LIB32DIR = lib32
DEB_HOST_LIB64DIR = lib


Those would later change once multiarch is ready:
DEB_HOST_LIBDIR   = lib/<arch native>-<os>
DEB_HOST_LIB32DIR = lib/<arch 32>-<os>
DEB_HOST_LIB64DIR = lib/<arch 64>-<os>


Why should dpkg-architecture care about them?
---------------------------------------------

Currently library placement differs between architectures and
even distributions (e.g. debian amd64 and ubuntu amd64) and finding
the right FHS compliant spot is a bit of a mess for packages. Instead
of duplicating this in every package a central location would be much
neater.

Having this in one place also alows to change it to the multiarch dirs
later and packages can easily be recompiled for the new locations.
Especialy while getting multiarch started this will be very helpfull
to have one source that works with both the old and the new place for
libs.


If you give me the go ahead I can supply a patch for this.

MfG
        Goswin

-- System Information:
Debian Release: 3.1
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.8-frosties-1
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages dpkg-dev depends on:
ii  binutils                      2.15-5     The GNU assembler, linker and bina
ii  cpio                          2.5-1.2    GNU cpio -- a program to manage ar
ii  make                          3.80-9     The GNU version of the "make" util
ii  patch                         2.5.9-2    Apply a diff file to an original
ii  perl [perl5]                  5.8.4-8    Larry Wall's Practical Extraction 
ii  perl-modules                  5.8.4-8    Core Perl modules

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to