Re: Enhanced syntax for Architecture field

On Thu, Mar 29, 2018 at 09:30:47AM +0200, Ole Streicher wrote: > Adam Borowski writes: > > The other change I'd make would be adding extra wildcards: > > * {big,little}-endian > > * {32,64,128¹}-bit > > * "fast" (and/or it's near-complement "slow") > > In principle, these could be simple dependen

Re: Enhanced syntax for Architecture field

Adam Borowski writes: > The other change I'd make would be adding extra wildcards: > * {big,little}-endian > * {32,64,128¹}-bit > * "fast" (and/or it's near-complement "slow") In principle, these could be simple dependencies: Either empty packages that exist only on the architectures fullfilling

Re: Enhanced syntax for Architecture field (Was: Usage of real m68k hardware)

On Wed, Mar 28, 2018 at 08:28:23PM +0200, Andreas Tille wrote: > On Wed, Mar 28, 2018 at 09:24:12PM +0300, Adrian Bunk wrote: > > > > Dependency fields have negative syntax like !m68k, for the Architecture: > > field this is only possible with a complete list of all architectures > > except the o

Enhanced syntax for Architecture field (Was: Usage of real m68k hardware)

Hi Adrian, On Wed, Mar 28, 2018 at 09:24:12PM +0300, Adrian Bunk wrote: > > Dependency fields have negative syntax like !m68k, for the Architecture: > field this is only possible with a complete list of all architectures > except the one you want to exclude. I agree this could really simplify t