diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101006/000871.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101006/000871.html | 98 |
1 files changed, 98 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101006/000871.html b/zarb-ml/mageia-dev/20101006/000871.html new file mode 100644 index 000000000..ef78eed7a --- /dev/null +++ b/zarb-ml/mageia-dev/20101006/000871.html @@ -0,0 +1,98 @@ +<!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=%3C20101005230405.GG21938%40mars-attacks.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="000870.html"> + <LINK REL="Next" HREF="000872.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] How will be the realese cycle?</H1> + <B>nicolas vigier</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=%3C20101005230405.GG21938%40mars-attacks.org%3E" + TITLE="[Mageia-dev] How will be the realese cycle?">boklm at mars-attacks.org + </A><BR> + <I>Wed Oct 6 01:04:05 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="000870.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI>Next message: <A HREF="000872.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#871">[ date ]</a> + <a href="thread.html#871">[ thread ]</a> + <a href="subject.html#871">[ subject ]</a> + <a href="author.html#871">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Wed, 06 Oct 2010, Tux99 wrote: + +><i> On Wed, 6 Oct 2010, nicolas vigier wrote: +</I>><i> +</I>><i> > > I think you misunderstood the concept proposed, we are not talking about +</I>><i> > > replacing cooker/cauldron, just merging updates and backports for the +</I>><i> > > 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> +But you can still use it while it is supported, and upgrade to a newer +realease when it's no more supported. + +><i> +</I>><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> +That's why backports repository is not enabled by default. + +><i> +</I>><i> 3) I mentioned earlier that the packager would need to use good +</I>><i> judgement and not include major incompatible version changes +</I> +There is always some small (and sometimes big) incompatibilities with +new versions. Not always known even by the developers. How should the +packager know about all the incompatibilities ? + +</PRE> + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000870.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI>Next message: <A HREF="000872.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#871">[ date ]</a> + <a href="thread.html#871">[ thread ]</a> + <a href="subject.html#871">[ subject ]</a> + <a href="author.html#871">[ 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> |