From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/20101006/000870.html | 85 +++++++++++++++++++++++++++++++++ 1 file changed, 85 insertions(+) create mode 100644 zarb-ml/mageia-dev/20101006/000870.html (limited to 'zarb-ml/mageia-dev/20101006/000870.html') diff --git a/zarb-ml/mageia-dev/20101006/000870.html b/zarb-ml/mageia-dev/20101006/000870.html new file mode 100644 index 000000000..0655554db --- /dev/null +++ b/zarb-ml/mageia-dev/20101006/000870.html @@ -0,0 +1,85 @@ + + + + [Mageia-dev] How will be the realese cycle? + + + + + + + + + +

[Mageia-dev] How will be the realese cycle?

+ Tux99 + tux99-mga at uridium.org +
+ Wed Oct 6 00:39:09 CEST 2010 +

+
+ +
On Wed, 6 Oct 2010, nicolas vigier wrote:
+
+> > I think you misunderstood the concept proposed, we are not talking about
+> > replacing cooker/cauldron, just merging updates and backports for the
+> > released version.
+> 
+> And then you run "urpmi --auto-select" on your server, and all your web
+> sites stop working because php was updated to a new version which is not
+> 100% compatible with the previous one ...
+
+Hmm, two things, actually three:
+
+1) I'd never use Mandriva on a server, because of the short support 
+period, a server OS requires at least 4-5 years support lifecycles
+(I'm not talking about MES here, just the normal Mandriva variants)
+
+2) from my experience "urpmi --auto-select" does that anyway, it doesn't 
+seem to differentiate between updates and backports (unlike drakrpm that 
+correctly ignores backports when checking for updates)
+
+3) I mentioned earlier that the packager would need to use good 
+judgement and not include major incompatible version changes
+
+
+ + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1