On Mon, Aug 02, 1999 at 11:36:19AM +0200, Roman Hodek wrote: > > > This shouldn't be too hard. You only need a syntax for it. There are several > > possibilities: > > > > Build-Depends: hurd-all:gnumach-dev, hurd-all:hurd-dev, > > linux-all:kernel-headers-2.0.36 > > The prefix idea is good, here a suggestion for concrete syntax: > > ARCH:package restricted to ARCH (all OSes)
Your naming is weird ;) s/ARCH/CPU/, s/OS/SYSTEM/ and I'm your friend. An example would be a bootloader, by the way, like GRUB (a program with special grub support on i386 machines could exploit this). > OS-*:package restricted to OS (all ARCHs) > OS-ARCH:package restricted to OS-ARCH > ARCH1|ARCH2:package more restrictions can be combined with '|', i.e. > package restricted to ARCH1 or ARCH2 > !ARCH:package restrictions can be negated with '!' Looks good to me. I don't know how many logical operators we should support, but it goes in the right direction. I am also unsure about the colon (:) as seperator. > > Build-Depends: texinfo > > Build-Depends-hurd-all: gnumach-dev, hurd-dev > > Build-Depends-linux-all: kernel-headers-2.0.36 > > This makes an inflation of field names :-) Agreed. I also think that the -Arch fields are overkill. Thanks, Marcus -- `Rhubarb is no Egyptian god.' Debian http://www.debian.org finger brinkmd@ Marcus Brinkmann GNU http://www.gnu.org master.debian.org [EMAIL PROTECTED] for public PGP Key http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ PGP Key ID 36E7CD09
