On 20/05/16 14:11, Kristian Fiskerstrand wrote: > >> keywording for a new arch should normally only be done when necessary, >> mainly if it is a direct dependency of another package. There is no need >> to keywor it for an arch until it has been tested on that arch by some >> user / developer ... certainly not because some committing developer >> think it is nice to have all arches listed just in case. >> > I should actually elaborate on this (in addition to fixing some spelling > errors..), something to the line of "There is no need to keyword it for > an arch until it is being _used_ by some user/developer on that arch" > My understanding as a prospective maintainer and dev, was that when you write an ebuild, you keyword the arches where /you personally/ have successfully built the package as ~arch . If you as maintainer or a user(s) then request stabilisation, that is where the arch teams, arch testing, etc. come into play. The only exception (if any!) is where amd64 and x86 often have an overlap whereby if it builds on one .. there's a good probability it will work on the other.
As far as fresh *new* arches to Gentoo, is this really a thing?! Surely we need a body of maintainers willing to support a new arch, and a new 'team' forming for such purposes, for bug fixes, stabilisation, etc. Sounds to me rather a case of simply misunderstanding what the KEYWORDS actually means and does in the context of Gentoo as a distro, else I've got the wrong end of the stick somewhere ....
signature.asc
Description: OpenPGP digital signature
