Clint Adams <[EMAIL PROTECTED]> writes: >> OK. Will "linux-libc-dev" be sufficient, or would a regex be better? >> i.e. will this contain a version number or some other variation >> (perhaps for non-Linux ports) in the name either now or at some point >> in the future? > > Previous state (since the inception of linux-kernel-headers up to what > will be the case for lenny): > > release arches= linux-kernel-headers > hurd= gnumach-dev, hurd-dev > kfreebsd= kfreebsd-kernel-headers > > Future state: > > release arches= linux-libc-dev > hurd= gnumach-dev, hurd-dev > kfreebsd= kfreebsd-kernel-headers
Does this look OK? It covers all the bases, but we might need to be a bit more intelligent about which gets used when. This should ideally be expressed in the same manner as a Depends line in the control file, so we can have arch-specific and alternative packages. [Sbuild/Conf.pm] our @toolchain_regex = ( 'binutils$', 'gcc-[\d.]+$', 'g\+\+-[\d.]+$', 'libstdc\+\+', 'libc[\d.]+-dev$', 'linux-kernel-headers$', 'linux-libc-dev$', 'gnumach-dev$', 'hurd-dev$', 'kfreebsd-kernel-headers$'); Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
pgp1EnnRqeuAQ.pgp
Description: PGP signature
