Re: Bug#41232: debian-policy: [PROPOSAL] Build-time dependencies on binary packages
On Mon, 2 Aug 1999, Roman Hodek wrote:
>
> > Your naming is weird ;) s/ARCH/CPU/, s/OS/SYSTEM/ and I'm your
> > friend.
>
> If it makes you lucky, think the vars re-named :-) But it really makes
> no difference, I meant exactly the same as you, i.e. ARCH == cpu.
>
> > 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.
>
> The | operator seems necessary when a package needs e.g.svglib on i386
> and alpha and nowhere else. The ! operator is necessary to avoid
> listings of all archs except one. Such lists have to be extended
> whenever there's a new Debian arch, and this calls for bugs.
>
> And I think the colon is as good or bad as anything else, so why not?
Can we use a format that is more inline with the rest of the depends
stuff? Perhaps:
pkg (>= 2.1 i386)
With the 'i386' being whatever specification you want to dream up.
(optional of course)
I would suggest that any depends element that has an unmet arch
specification would simply be ignored (evaluate to 'true').
Jason
Reply to: