diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-July/006719.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-July/006719.html | 108 |
1 files changed, 108 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-July/006719.html b/zarb-ml/mageia-dev/2011-July/006719.html new file mode 100644 index 000000000..db778d99d --- /dev/null +++ b/zarb-ml/mageia-dev/2011-July/006719.html @@ -0,0 +1,108 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] new mgarepo version + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20new%20mgarepo%20version&In-Reply-To=%3C1310811622.3728.292.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="006713.html"> + <LINK REL="Next" HREF="006722.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] new mgarepo version</H1> + <B>Michael Scherer</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20new%20mgarepo%20version&In-Reply-To=%3C1310811622.3728.292.camel%40akroma.ephaone.org%3E" + TITLE="[Mageia-dev] new mgarepo version">misc at zarb.org + </A><BR> + <I>Sat Jul 16 12:20:22 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="006713.html">[Mageia-dev] new mgarepo version +</A></li> + <LI>Next message: <A HREF="006722.html">[Mageia-dev] new mgarepo version +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6719">[ date ]</a> + <a href="thread.html#6719">[ thread ]</a> + <a href="subject.html#6719">[ subject ]</a> + <a href="author.html#6719">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le samedi 16 juillet 2011 à 11:36 +0200, Samuel Verschelde a écrit : +><i> Le samedi 16 juillet 2011 03:02:21, Michael Scherer a écrit : +</I> +><i> > Wasn't it against the policy ( ie, this is neither a bugfix, this is a +</I>><i> > version update, providing feature ) ? +</I>><i> +</I>><i> Strictly speaking, maybe, but the policy says "Things are not set in stone, +</I>><i> but we need a policy to move ahead with releasing updates for mga1, and we can +</I>><i> refine the process as we find issues/shortcomings.", and I think this is one of +</I>><i> the cases where we can allow updates, to ease packager's work. We could add +</I>><i> "updates of mageia distribution building tools are allowed to ensure that +</I>><i> packagers using stable releases have the same tools than those using cauldron" +</I> +Personally, I would prefer that we first refine the policy and then act +rather than the contrary :) + +And so, if we provides newer version of tools, what is wrong with using +backports for that ? + +I am not keen on pushing our newer tool on update, since we plan to have +our server using mageia, and so in the futur, if we push newer iurt, +mgarepo, rpmlint, they may potentially disrupt build system. So by being +clear and using backports, we would avoid such problem more easily. + +-- +Michael Scherer + +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="006713.html">[Mageia-dev] new mgarepo version +</A></li> + <LI>Next message: <A HREF="006722.html">[Mageia-dev] new mgarepo version +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6719">[ date ]</a> + <a href="thread.html#6719">[ thread ]</a> + <a href="subject.html#6719">[ subject ]</a> + <a href="author.html#6719">[ 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> |