1 |
tis 2001-12-25 klockan 16.49 skrev Daniel Robbins: |
2 |
> On Tue, Dec 25, 2001 at 01:10:02PM +0100, Mikael Hallendal wrote: |
3 |
> > Well, it's very much unsolved. Because users don't care about masking |
4 |
> > once they've learned how to get around it. As I said before _beta, |
5 |
> > masking will only hold back some and tell that it's unstable. But we'll |
6 |
> > end up supporting the stuff anyway. |
7 |
> |
8 |
> This is easily solved. Just put a very clear comment in package.mask around |
9 |
> the mask entries stating in no unclear terms that *these packages are not yet |
10 |
> supported*, are *for developers only*, and *are very unstable*. *use at your |
11 |
> own risk*, *not a good idea* and *you'll regret it later* should do the trick! |
12 |
> :) |
13 |
> |
14 |
> > This is just as the /incoming directory which many users started to use |
15 |
> > even though they shouldn't. |
16 |
> |
17 |
> How so? |
18 |
|
19 |
The ebuilds in /incoming are untested and should not be used by users. |
20 |
But since it's available to users, users use it anyway. |
21 |
|
22 |
I think it all comes down to what kind of distribution we want to |
23 |
create. If we want to make a distribution for those that create it and |
24 |
use-at-own-risk for everyone else (this is all fine by me) we should |
25 |
clearly state this (to users and developers). |
26 |
|
27 |
If we want to create a distributions for everyone we have to go around |
28 |
to make users don't hurt themeselfs. Since users _will_ do bad things to |
29 |
there own systems if they are able to. And if so, masking and comments |
30 |
are not enough, imho. |
31 |
|
32 |
CVS branches solves these problems (and we have to start using branches |
33 |
sooner or later anyway, preferable when we release 1.0). |
34 |
|
35 |
Regards, |
36 |
Mikael Hallendal |
37 |
|
38 |
-- |
39 |
|
40 |
Mikael Hallendal |
41 |
Gentoo Linux Developer, Desktop Team Leader |
42 |
CodeFactory AB, Stockholm, Sweden |