1 |
On Friday 03 of October 2008 04:14:54 Jeroen Roovers wrote: |
2 |
> On Thu, 2 Oct 2008 17:56:39 -0700 |
3 |
> |
4 |
> "Alec Warner" <antarus@g.o> wrote: |
5 |
> > If pmask is not for testing...what is it for? |
6 |
> |
7 |
> The name says it all - to prevent people from automatically emerging |
8 |
> stuff, even when ACCEPT_KEYWORDS=~arch is set. First you try for the new |
9 |
> version: |
10 |
> |
11 |
> # emerge -va www-client/opera |
12 |
> |
13 |
> which doesn't work (it gives you the current version!). Then you try |
14 |
> with a specific version: |
15 |
> |
16 |
> # emerge -va =www-client/opera-9.6* |
17 |
> |
18 |
> which gives you a good reason to either unmask or not unmask: |
19 |
> |
20 |
> !!! All ebuilds that could satisfy "=www-client/opera-9.6*" have been |
21 |
> masked. !!! One of the following masked packages is required to |
22 |
> complete your request: |
23 |
> - www-client/opera-9.60_pre2440 (masked by: package.mask) |
24 |
> /keeps/gentoo/portage/profiles/package.mask: |
25 |
> # Jeroen Roovers <jer@g.o> (26 Aug 2008) |
26 |
> # www-client/opera snapshots are masked. Please read |
27 |
> # http://my.opera.com/desktopteam/blog/ |
28 |
> |
29 |
> - www-client/opera-9.60_pre2436 (masked by: package.mask) |
30 |
> - [...] |
31 |
> |
32 |
> If it merely says that the masking is for "testing" (and especially if |
33 |
> testing takes many months and apparently takes place in secret) the |
34 |
> whole point is lost on the people who have come so far and still want to |
35 |
> press on - they'll simply ignore your "warning against testing". |
36 |
|
37 |
Same way one may see "masked by missing keyword" note and interprete as "not |
38 |
for your arch"... So a quick note in p.mask can say it is for testing |
39 |
purposes, so user can choose either to install it or not. |
40 |
|
41 |
> |
42 |
> There are various valid reasons, but testing means you want to expose |
43 |
> stuff, not hide it. There's simply no way you'd package.mask something, |
44 |
> and at the same time explain you want it tested. Because you're |
45 |
> preventing most ~arch systems from getting automatically widely exposed |
46 |
> to the stuff you're intending to get tested. |
47 |
|
48 |
I don't think it's ok. ~arch isn't training ground. It's supposed to work, so |
49 |
asking arch teams to keywords packages that are not supposed to work isn't |
50 |
good. |
51 |
|
52 |
> |
53 |
> Even saying that it would kill puppies would be more valid. Just be |
54 |
> honest and tell people what is going on. Tell them that if they use |
55 |
> Opera snapshots, they shouldn't care about losing mail or experience |
56 |
> frequent crashes while browsing. Anything really, just don't tell them |
57 |
> you're "testing" or you find yourself excluding them from the party |
58 |
> with a really bad excuse. |
59 |
|
60 |
This is the place i agree with you. Anyway i think package still should be |
61 |
p.masked with good explanation of why it is masked. |
62 |
|
63 |
-- |
64 |
Cheers, |
65 |
Dawid Węgliński |