1 |
Hi, |
2 |
since I aint got blag i will polute our lovely mailing list (sorry if i hit |
3 |
some in-middle flame :P). |
4 |
|
5 |
Currently i've been reviewing the package.mask file (since we have to keep with |
6 |
it for a while [no package.mask folder near us :)] we have to trim it down and |
7 |
keep sane). |
8 |
|
9 |
NOTE: The p.mask as folder situation was agreed upon so dont reply about THAT |
10 |
but focus on what follows below this point in your replies. |
11 |
|
12 |
While i was reading it there are 5 major use cases for stuff in it. |
13 |
|
14 |
- Masking beta/rc/alpha/development_branch stuff |
15 |
- Masking live ebuild |
16 |
- Masking stable releases for testing |
17 |
- Masks for removal (those are quite moving in and out ;]) |
18 |
- Masks for security issues (mostly games) |
19 |
|
20 |
So lets go one by one and rationalize on wether we need it or not. |
21 |
|
22 |
* Masking beta... |
23 |
This masks are good if the software release is KNOWN to break previous |
24 |
behaviour or degrade user experience. Otherwise the software should not be |
25 |
masked (its TESTING for purpose, not stable). |
26 |
Also the maintainer should watch if the testing branch is still relevant (why |
27 |
on earth we have masked 4.0.3_p20070403 version of screen when newer 4.3 is |
28 |
stable ;]) and remove the branch+mask when needed. |
29 |
|
30 |
* Masking live... |
31 |
Heck no. This is not proper usage. Just use keywords mask. KEYWORDS="". |
32 |
Problem solved and the package.mask is smaller. (Note, in overlays do what |
33 |
ever you want, since it does not polute the main mask from g-x86). |
34 |
|
35 |
* Masking stable releases... |
36 |
Here i found most interesting stuff around (for example mask for testing from |
37 |
2006, yeah not ~ material after 3 years?! :P) |
38 |
There should be policy defined that you can add the new release under p.mask if |
39 |
you see it fit, but the mask can stay only for 6 months (less/more, |
40 |
suggestions?) and then it must be unmasked, or have really high activity on |
41 |
tracker bug and good reasoning (mask for ruby-1.9 and so on). |
42 |
|
43 |
* Masks for removal... |
44 |
Nothing to say here, they are done quite well right now, and treecleaners kill |
45 |
them when they got time :] |
46 |
|
47 |
* Masks for security... |
48 |
These are the only one masks that are permanent (probably none will fix the |
49 |
nethack,...). They should be maybe even kept on the bottom of the package.mask |
50 |
file all together and separated with some comment, so they are always easy to |
51 |
spot from first look on that file. |
52 |
|
53 |
Any more ideas/suggestions to the above? |
54 |
|
55 |
Cheers |
56 |
|
57 |
-------- |
58 |
Tomáš Chvátal |
59 |
Gentoo Linux Developer [KDE/Overlays/QA/Sunrise/X11] |
60 |
E-Mail : scarabeus@g.o |
61 |
GnuPG FP : 94A4 5CCD 85D3 DE24 FE99 F924 1C1E 9CDE 0341 4587 |
62 |
GnuPG ID : 03414587 |