Re: smarter way to differ architectures needed?

[Gordon Matzigkeit <gord@trick.fig.org>]

>>>>> Marcus Brinkmann writes:

 MB> This is less complex then the current mechanism, because we only
 MB> need "provide" and "depends", and hopefully not "conflicts" and
 MB> "replaces".

No package needs Conflicts and Replaces.  They are just shorthands for
Provides (given that two packages cannot Provide the same thing, which
I assume is the current implementation):

A Conflicts B == A Provides C, B Provides C
A Replaces B == A Provides B

-- 
 Gordon Matzigkeit <gord@fig.org>  //\ I'm a FIG (http://www.fig.org/)
Committed to freedom and diversity \// I use GNU (http://www.gnu.org/)