On 3/18/20 10:54 AM, William Hubbs wrote: > > 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. >
This is a good goal, but as others have pointed out, adding a new magic keyword poses some workflow problems. We already have the ability to fake this. Instead of KEYWORDS="~noarch", if you really believe that your package is architecture-independent, you can just add all ~arch keywords to it. If you're right, no one will ever notice, and if you're wrong, you'll get shit for it -- just like you would have if you marked it ~noarch incorrectly. Maintainers can do their own stabilization (on all arches) for those packages. I hesitate to invoke "common sense," but in cases where common sense truly does prevail, you should have no problem keywording and stabilizing a package on all arches that e.g. downloads a PDF of API documentation.
