summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-June/005616.html
blob: b171885736e34b51d7056c1c26d1544c75c53d39 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] Release cycles proposals, and discussion
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Release%20cycles%20proposals%2C%20and%20discussion&In-Reply-To=%3C1308059026.24304.211.camel%40akroma.ephaone.org%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="005670.html">
   <LINK REL="Next"  HREF="005621.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Release cycles proposals, and discussion</H1>
    <B>Michael Scherer</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Release%20cycles%20proposals%2C%20and%20discussion&In-Reply-To=%3C1308059026.24304.211.camel%40akroma.ephaone.org%3E"
       TITLE="[Mageia-dev] Release cycles proposals, and discussion">misc at zarb.org
       </A><BR>
    <I>Tue Jun 14 15:43:45 CEST 2011</I>
    <P><UL>
        <LI>Previous message: <A HREF="005670.html">[Mageia-dev] Release cycles proposals, and discussion
</A></li>
        <LI>Next message: <A HREF="005621.html">[Mageia-dev] Release cycles proposals, and discussion
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#5616">[ date ]</a>
              <a href="thread.html#5616">[ thread ]</a>
              <a href="subject.html#5616">[ subject ]</a>
              <a href="author.html#5616">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Le mardi 14 juin 2011 &#224; 07:55 +0200, Thorsten van Lil a &#233;crit :
&gt;<i> Am Montag, 13. Juni 2011, 23:28:04 schrieb Renaud MICHEL:
</I>&gt;<i> &gt; On lundi 13 juin 2011 at 23:06, Thorsten van Lil wrote :
</I>&gt;<i> &gt; &gt; A rolling release has following advantages:
</I>&gt;<i> &gt; &gt; 1. the distribution is always up to date (also hardware support)
</I>&gt;<i> &gt; &gt; 2. no re-install over and over again
</I>&gt;<i> &gt; 
</I>&gt;<i> &gt; I don't get it why people think a re-install is necessary.
</I>&gt;<i> &gt; My current computer was installed with mandriva 2007 (don't remember if it
</I>&gt;<i> &gt; was .0 or .1), it is now mageia 1 and has been updated to all intermediary
</I>&gt;<i> &gt; mdv releases.
</I>&gt;<i> 
</I>&gt;<i> An Upgrade is nearly the same, than reinstalling. The difference is only, that 
</I>&gt;<i> you can use your system in the mean time and you are not forced to install the 
</I>&gt;<i> missing packages. 
</I>
Rolling is just the same as upgrade, except it take X months to do it
with a small change everyday instead of having thing upgraded every X
months.

&gt;<i> &gt; &gt; This could look like this:
</I>&gt;<i> &gt; &gt; Bring up a release once a year. The core (kernel, glib, ...) will only
</I>&gt;<i> &gt; &gt; get  minor updates. Apllications like firefox, libreoffice, ... will
</I>&gt;<i> &gt; &gt; always be up to date (rolling). Maybe also the desktop envirenments
</I>&gt;<i> &gt; &gt; could be rolling but this is very heavy.
</I>&gt;<i> &gt; 
</I>&gt;<i> &gt; If I understood correctly, that is exactly what the backports should
</I>&gt;<i> &gt; provide, new versions of programs when possible (no update of half of the
</I>&gt;<i> &gt; core system libraries).
</I>&gt;<i> &gt; 
</I>&gt;<i> 
</I>&gt;<i> Yes, but Backports are not officially supported and we wouldn't advice new users 
</I>&gt;<i> to backports normally. 
</I>
I am sorry, but I fail to follow your reasoning.

Why wouldn't you do a comparison where in one case not recommend
backports, and in the others, recommend them for the whole system ?

If this is for ressource related reasons, why would we have the
ressources in one case and not in the others ? 

And as I said in another mail, if people want to follow arch linux and
do a better job, maybe they should start to explain what are the weak
points of the distribution and then do proposal on stuff that can be
done better instead of asking to copy cat hoping this would be better.

-- 
Michael Scherer

</PRE>






















































































<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="005670.html">[Mageia-dev] Release cycles proposals, and discussion
</A></li>
	<LI>Next message: <A HREF="005621.html">[Mageia-dev] Release cycles proposals, and discussion
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#5616">[ date ]</a>
              <a href="thread.html#5616">[ thread ]</a>
              <a href="subject.html#5616">[ subject ]</a>
              <a href="author.html#5616">[ author ]</a>
         </LI>
       </UL>

<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>