diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/005994.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-June/005994.html | 124 |
1 files changed, 124 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/005994.html b/zarb-ml/mageia-dev/2011-June/005994.html new file mode 100644 index 000000000..869af4df0 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/005994.html @@ -0,0 +1,124 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Backports policy proposal + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20policy%20proposal&In-Reply-To=%3C201106241619.46153.bgmilne%40staff.telkomsa.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="005983.html"> + <LINK REL="Next" HREF="006006.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Backports policy proposal</H1> + <B>Buchan Milne</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20policy%20proposal&In-Reply-To=%3C201106241619.46153.bgmilne%40staff.telkomsa.net%3E" + TITLE="[Mageia-dev] Backports policy proposal">bgmilne at staff.telkomsa.net + </A><BR> + <I>Fri Jun 24 16:19:45 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="005983.html">[Mageia-dev] Backports policy proposal +</A></li> + <LI>Next message: <A HREF="006006.html">[Mageia-dev] Backports policy proposal +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5994">[ date ]</a> + <a href="thread.html#5994">[ thread ]</a> + <a href="subject.html#5994">[ subject ]</a> + <a href="author.html#5994">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Friday, 24 June 2011 08:30:15 Maarten Vanraes wrote: +><i> Op vrijdag 24 juni 2011 02:10:14 schreef Michael Scherer: +</I>><i> [...] +</I>><i> +</I>><i> > Another rule that we could add is that cauldron should always be newer +</I>><i> > than backports, in order to ensure upgradability. The same goes for n-2 +</I>><i> > and n-1 release. +</I>><i> > While this seems innocent, do not forget this will have a impact when we +</I>><i> > do the version freeze. +</I>><i> +</I>><i> [..] +</I>><i> +</I>><i> This seems hard to enforce... i can imagine if you make backport, it has +</I>><i> essentially the same version as in cauldron, i can think that there is a +</I>><i> few spec file changes that are only for backports, +</I> +Why should it need spec file changes? + +><i> and thus the release +</I>><i> becomes newer than the one in cauldron +</I> +If it requires spec file changes, why should cauldron not get a new release +that includes the changes? + +Sorry, but a number of my packages were regularly backported, and I never +needed cooker to be older ... + +Regards, +Buchan +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="005983.html">[Mageia-dev] Backports policy proposal +</A></li> + <LI>Next message: <A HREF="006006.html">[Mageia-dev] Backports policy proposal +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5994">[ date ]</a> + <a href="thread.html#5994">[ thread ]</a> + <a href="subject.html#5994">[ subject ]</a> + <a href="author.html#5994">[ 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> |