On Wed, 2020-03-18 at 09:54 -0500, William Hubbs wrote: > this came up again on the recent thread about dropping non x86/amd64 > support for python packages, and I want to bring it up again on its own > thread. > > How often do architecture specific bugs really exist in languages like > perl, python etc? From what I've seen they are pretty rare. Not to mention, > if we found one somewhere, we could adjust keywords as necessary. > > Also, if someone did inadvertently keyword a package with noarch that didn't > work everywhere, it would be a matter of adjusting the keywords for that > package. > > So, my question is, why can't we add a noarch/~noarch keyword and see > how things go? If it gets abused we can always nuke it later. >
1. How is this going to work when noarch package depends on non-nonarch package? I mean, will all the package managers actually work? Have you did some minimal testing before bringing this up? 2. Who will be responsible for handling noarch stablereqs? Will there be a noarch arch team? -- Best regards, Michał Górny
signature.asc
Description: This is a digitally signed message part
