Re: Bug#748936: apt doesnt understand architecture wildcards
"Bernhard R. Link" <brlink@debian.org> writes:
> Urgh. Really? This is far too complicated for most programs to implement
> properly. I'd suggest to rather fix dpkg (and also fix policy.
Policy should obviously track dpkg, which is currently canonical for how
wildcards work since it contains the primary implementation. If you think
this should change, you should first convince the dpkg maintainers, and
then raise this with Policy after dpkg has changed.
> The footnote describes absolutely nothing currently,
It does describe something to me, but I'm probably too close to it. We're
certainly happy to consider alternative wording.
> 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.
That said, Policy could probably stand to provide more guidance on how to
interpret the results of dpkg-architecture -L and how they map to wildcard
strings.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: