Hi! On Sat, 2003-11-01 at 13:47:30 +0100, Robert Millan wrote: > Package: debhelper > Version: 4.1.77 > Severity: wishlist
> I'm working on the Glibc-based GNU/KNetBSD port, and have some problems with > the way debhelper determines its arch-specific files in debian/ directory. > > Due to restrictions in the criteria used by dpkg maintainers to assign > architecture names, we're having to use the same name "netbsd-i386" for both > the port based on Glibc and the one using NetBSD's C library. > > Then if the people working on NetBSD-libc add something (which they have done) > like "debian/foo.install.netbsd-i386", it affects both ports and breaks for > the > Glibc-based one. This should not be the case, at least nowadays. The requirement is that an arch should be bijective when it comes to its mapping between Debian and GNU tuples/triplets. > We have, however, distinct system triplets. So if instead of looking for: > > debian/foo.install.$(DEB_BUILD_ARCH) > > debhelper looked for: > > debian/foo.install.$(DEB_BUILD_GNU_TYPE) > > We could solve the problem in a flexible way. Would you like to do that? > (and rising DH_COMPAT accordingly, etc). So (besides this probably having been meant as s/BUILD/HOST/) it seems this is not needed. There are further requests to allow for cpu/os-specific files, but I'm not sure there's a need for those either? Or if there is it's so fringy they can be handled ad-hoc? Thanks, Guillem
