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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] How will be the realese cycle?
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3C201010061614.09432.bgmilne%40multilinks.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="000897.html">
<LINK REL="Next" HREF="000902.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] How will be the realese cycle?</H1>
<B>Buchan Milne</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3C201010061614.09432.bgmilne%40multilinks.com%3E"
TITLE="[Mageia-dev] How will be the realese cycle?">bgmilne at multilinks.com
</A><BR>
<I>Wed Oct 6 17:14:09 CEST 2010</I>
<P><UL>
<LI>Previous message: <A HREF="000897.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI>Next message: <A HREF="000902.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#901">[ date ]</a>
<a href="thread.html#901">[ thread ]</a>
<a href="subject.html#901">[ subject ]</a>
<a href="author.html#901">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Tuesday, 5 October 2010 23:39:09 Tux99 wrote:
><i> On Wed, 6 Oct 2010, nicolas vigier wrote:
</I>><i> > > I think you misunderstood the concept proposed, we are not talking
</I>><i> > > about replacing cooker/cauldron, just merging updates and backports
</I>><i> > > for the released version.
</I>><i> >
</I>><i> > And then you run "urpmi --auto-select" on your server, and all your web
</I>><i> > sites stop working because php was updated to a new version which is not
</I>><i> > 100% compatible with the previous one ...
</I>><i>
</I>><i> Hmm, two things, actually three:
</I>><i>
</I>><i> 1) I'd never use Mandriva on a server, because of the short support
</I>><i> period, a server OS requires at least 4-5 years support lifecycles
</I>><i> (I'm not talking about MES here, just the normal Mandriva variants)
</I>
Who said anything about Mandriva?
What would convince you to run Mageia on a server (assuming e.g. a 4-5 year
support lifecycle).
BTW., I know quite a lot of people that run Mandriva on servers ...
><i> 2) from my experience "urpmi --auto-select" does that anyway, it doesn't
</I>><i> seem to differentiate between updates and backports (unlike drakrpm that
</I>><i> correctly ignores backports when checking for updates)
</I>
Use --update option, or 'urpmi --auto-update'.
><i> 3) I mentioned earlier that the packager would need to use good
</I>><i> judgement and not include major incompatible version changes
</I>
You are aware that this is significantly more work than 'mdvsys submit -t
2010.1 --define section=main/backports $package' (after some minimal testing of
course)?
Regards,
Buchan
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000897.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI>Next message: <A HREF="000902.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#901">[ date ]</a>
<a href="thread.html#901">[ thread ]</a>
<a href="subject.html#901">[ subject ]</a>
<a href="author.html#901">[ 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>
|
