1 |
Hi Rainer, |
2 |
|
3 |
I forgot (again...) to cc gentoo-dev. I've resend my earlier message to |
4 |
the list and I'll cc my reply now too. |
5 |
|
6 |
On Sunday, Dec 15, 2002, at 15:02 Europe/Brussels, Rainer Groesslinger |
7 |
wrote: |
8 |
> |
9 |
>>> Currently the package.mask carries packages which have a right to be |
10 |
>>> called |
11 |
>>> unstable, e.g. XFree 4.2.99 and so on... |
12 |
>>> But the stable/unstable situation in some ebuilds is a bit confusing |
13 |
>>> and |
14 |
>>> leading in the wrong direction if continued like this ? |
15 |
>> |
16 |
>> Can you give an example of these ebuilds? |
17 |
>> |
18 |
>> I know there are some apps which are called unstable by their |
19 |
>> developer, and stable by us. But this happens only after a long period |
20 |
>> of testing/running the app. |
21 |
|
22 |
> Let's take an application a lot of people use: |
23 |
> Mozilla |
24 |
> We have these ebuilds for Mozilla: |
25 |
> |
26 |
> mozilla-1.0-r3.ebuild |
27 |
> mozilla-1.0.1-r3.ebuild |
28 |
> mozilla-1.1-r1.ebuild |
29 |
> mozilla-1.2.1-r1.ebuild |
30 |
> mozilla-1.2.1-r2.ebuild |
31 |
> |
32 |
> 1.2.1-r1, 1.2.1-r2 and 1.1-r1 use ~x86 that means someone who uses |
33 |
> stable is |
34 |
> getting 1.0.1-r3 |
35 |
> Does that make sense ? As you said the build process etc. is a reason |
36 |
> for |
37 |
> calling something unstable, too, sure :) |
38 |
|
39 |
There are different reasons for an ebuild to be called unstable: |
40 |
|
41 |
- security |
42 |
- upstream dev sells it as unstable |
43 |
- testing |
44 |
- building process fails |
45 |
|
46 |
I this case I would say: |
47 |
|
48 |
mozilla-1.1-r1.ebuild: Not sure why this is marked unstable (could be |
49 |
anything - i suspect either the upstream devs sell it as unstable, or |
50 |
it is still in testing (source code was patched only a few days ago)) |
51 |
|
52 |
mozilla-1.2.1-r1.ebuild: Was in testing fase (but apparently some minor |
53 |
problems were discovered and a new release was made) - only 8 days old |
54 |
|
55 |
revision 1.4 |
56 |
date: 2002/12/15 10:44:21; author: bjb; state: Exp; lines: +2 -2 |
57 |
During removal of sparc64 keywords from the ebuilds a bad sed |
58 |
introduced problematic KEYWORDS line that contained an illegal |
59 |
character before the alpha keyword. Fixed. |
60 |
---------------------------- |
61 |
revision 1.3 |
62 |
date: 2002/12/09 20:17:53; author: azarah; state: Exp; lines: +14 -10 |
63 |
add more moznoxft checks; fix NSS headers not all installing |
64 |
---------------------------- |
65 |
revision 1.2 |
66 |
date: 2002/12/09 04:33:20; author: manson; state: Exp; lines: +2 -2 |
67 |
12-08-02 Keyword change remove sparc64 Rodney Rees manson@g.o |
68 |
---------------------------- |
69 |
revision 1.1 |
70 |
date: 2002/12/08 21:39:49; author: azarah; state: Exp; |
71 |
some bugfixes |
72 |
|
73 |
|
74 |
|
75 |
|
76 |
mozilla-1.2.1-r2.ebuild: In testing fase now (only two days old) |
77 |
---------------------------- |
78 |
revision 1.3 |
79 |
date: 2002/12/15 07:43:55; author: azarah; state: Exp; lines: +3 -3 |
80 |
add missing Xrender include and lib dirs |
81 |
---------------------------- |
82 |
revision 1.2 |
83 |
date: 2002/12/14 17:34:43; author: azarah; state: Exp; lines: +4 -1 |
84 |
make sure old Xft and Xrender libs are removed |
85 |
---------------------------- |
86 |
revision 1.1 |
87 |
date: 2002/12/14 17:26:07; author: azarah; state: Exp; |
88 |
update Xft and Xrender. add _moz to libXft and libXrender to try and |
89 |
fix the mozilla not always starting bug |
90 |
|
91 |
|
92 |
> Perhaps not the perfect example but I doubt someone who is running |
93 |
> Mozilla |
94 |
> 1.0.1 is running a more stable Mozilla than someone who is running |
95 |
> 1.2.1 (of |
96 |
> course there are other things, too like in stable galeon etc. should |
97 |
> all be |
98 |
> compatible to the used Mozilla version and so on[and current versions |
99 |
> of |
100 |
> these apps are compatible with newer mozilla versions so that can't be |
101 |
> the |
102 |
> reason for 1.0.1 being the latest 'stable'). |
103 |
|
104 |
I think in this case the ebuild author wanted to make sure mozilla-1.2 |
105 |
build process works before marking the ebuild as stable. (see the |
106 |
changelog - there seem to be a lot of issues with it.) I don't know |
107 |
anything about Mozilla 1.1 (the authors comment sounded rather negative |
108 |
a few months ago - but maybe its time to mark this as stable unless if |
109 |
upstream devs sell it as unstable). Mozilla1.0 is apparently the only |
110 |
version that works without real problems on all computers right now. |
111 |
|
112 |
> I believe you are right I just don't get it since I am not a Gentoo |
113 |
> dev but |
114 |
> I just wondered... |
115 |
> |
116 |
> Rainer |
117 |
> |
118 |
> PS: You replied to me and not to the list, so I reply to you only |
119 |
> again - |
120 |
> just a hint if it was unwanted |
121 |
|
122 |
hehe |
123 |
|
124 |
Pieter |
125 |
|
126 |
|
127 |
-- |
128 |
gentoo-dev@g.o mailing list |