On Thu, 11 Aug 2022, Dan Čermák wrote:
Richard Biener
writes:
[..]
The suggestion of multiple repositories is just one possible technical implementation of such annotation, using system provides and package requires would be another (then with the technical issue of having multiple same named but different filenamed packages in the same repository?).
[OT] Why requires though? I don't think it's a good idea to explicitly require a library with a certain instruction set. Provides on the other hand would be a workaround, but I really think that architectures are the proper way how this should be handled.
To elaborate, the "system" would have a Provides: hw-x86_64-version = 3
for example and a package built for x86_64-v2 would then have a
Requires: hw-x86_64-version >= 2. The Provides would be magically
added upon install time somehow (thus "system provides"). The
provides/requires would then be the high-level implementation
or as to say, a safety net. That could be done ontop of the multiple
repositories.
But sure, it would weirdly exist besides the rpm architecture but
as I know that one is a mess it's maybe better to not rely on it
in the short term.
Richard.
--
Richard Biener