Bug#498300: specify that architecture-specific dependencies must have a non-empty list of architectures
Stefano Zacchiroli dijo [Fri, Sep 19, 2008 at 01:46:05PM +0200]:
> (...)
> As per policy the empty architecture list has no defined semantics, I
> guess that the only possible behaviours out there are the following:
>
> 1) require at least one entry (as did by python-debian)
>
> 2) assume a default polarity, this in turn would lead to one of the
> possible two semantics:
>
> a) (polarity positive) hence empty arch list means "no architecture",
> i.e. useless dependency
>
> b) (polarity negative) hence empty arch list means "no excluded
> architecture", i.e. always present dependency
>
> We can start betting on this possibilities :-)
Umh... And I think I'd rather go with the negative polarity. This
means that [] is a no-op. Positive polarity just kills all the
dependency information for that dependency... And I doubt it is ever
desirable!
--
Gunnar Wolf - gwolf@gwolf.org - (+52-55)5623-0154 / 1451-2244
PGP key 1024D/8BB527AF 2001-10-23
Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF
Reply to: