Re: Bug#748936: apt doesnt understand architecture wildcards
* Russ Allbery <firstname.lastname@example.org> [140525 22:58]:
> > and having such important fields a meaning that you cannot calculate
> > without knowing what architectures the system finally using the package
> > uses makes it unhandable).
> I'm not completely sure what you mean by this, but if you mean that you
> can't know what architecture strings are valid without knowing which
> architectures are supported by dpkg, I think that's a feature in Policy,
> not a bug. I wouldn't want to update Policy every time a new architecture
> was added. That happens quite frequently.
I mean that no tool can give meaning to those strings without having the
full architecture table of the dpkg on the machine where this is to be
finally interpreted. (Which especially means that any tools trying to
interprete anything with those wildcards needs something from a dpkg
that already knows those architectures.).
Something like a "any-FOO" matching any debian architecture "*-FOO" and
"FOO" would be something simple.
Having magic like any-arm also matching armhf means it cannot be
processed without having special knowledge of the architectures.
Bernhard R. Link
F8AC 04D5 0B9B 064B 3383 C3DA AFFC 96D1 151D FFDC