As set out in bug #304435 [1], we should declare some policy about changes to arch profiles in devmanual or in the Developer Handbook.
Basically, I would want to have this apply to arch profile changes as well: [5] http://devmanual.gentoo.org/keywording/index.html says: = Keywording on Upgrades = [...] Sometimes you may need to remove a keyword because of new unresolved dependencies. If you do this, you *must* file a bug notifying the relevant arch teams. since it all to often happens that this isn't done, or is done after the fact. It would be even more helpful to get some language in there advising ebuild developers to coordinate this with the relevant arch teams in advance so that keywords need not be dropped at all, or that the package.mask entry can be minimised, or that damage can be limited in whichever way is technically achievable. The documentation about maintaining sub-profiles is thin already, so we might as well start documenting it more generally as well. Regards, jer [1] https://bugs.gentoo.org/show_bug.cgi?id=304435