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