Von: Dominique Leuenberger / DimStar

The proposal I favor so far is the 'possible option' - i.e allow to build everything (or as much as we want) proprely as a different architecture and get this into rpm/zypp. mls has already been lined up and thinks it should be rather easy (for the rpm and obs part);

It may be easy code-wise, but we would need rpm upstream to accept the new architecture. Plus, we'll need to adapt many spec files to use a new %x86_64 macro in ifarch lines. I'm actually in favor of the ld.so hwcaps subdirectory feature, for a couple of reasons: - all the container tooling does not support a way to differentiate x86_64 - the v3 package can still be installed in parallel on a host that does not support it, i.e. one can build containers that have both versions installed - there is no need for a new architecture in the build service, we can build the v3 variants in the x86_64 scheduler (using multibuild or package links). Hwcaps has the disadvantage that it only works for libraries, though. Cheers, Michael. -- Michael Schroeder SUSE Software Solutions Germany GmbH mls@suse.de GF: Ivo Totev HRB 36809, AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}