diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-July/006722.html')
-rw-r--r-- | zarb-ml/mageia-dev/2011-July/006722.html | 113 |
1 files changed, 113 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-July/006722.html b/zarb-ml/mageia-dev/2011-July/006722.html new file mode 100644 index 000000000..ad7433854 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-July/006722.html @@ -0,0 +1,113 @@ +<!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=%3C201107161234.42616.stormi%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="006719.html"> + <LINK REL="Next" HREF="006734.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] new mgarepo version</H1> + <B>Samuel Verschelde</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20new%20mgarepo%20version&In-Reply-To=%3C201107161234.42616.stormi%40laposte.net%3E" + TITLE="[Mageia-dev] new mgarepo version">stormi at laposte.net + </A><BR> + <I>Sat Jul 16 12:34:42 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="006719.html">[Mageia-dev] new mgarepo version +</A></li> + <LI>Next message: <A HREF="006734.html">[Mageia-dev] new mgarepo version +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6722">[ date ]</a> + <a href="thread.html#6722">[ thread ]</a> + <a href="subject.html#6722">[ subject ]</a> + <a href="author.html#6722">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le samedi 16 juillet 2011 12:20:22, Michael Scherer a écrit : +><i> Le samedi 16 juillet 2011 à 11:36 +0200, Samuel Verschelde a écrit : +</I>><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 +</I>><i> > stone, but we need a policy to move ahead with releasing updates for +</I>><i> > mga1, and we can refine the process as we find issues/shortcomings.", +</I>><i> > and I think this is one of the cases where we can allow updates, to ease +</I>><i> > packager's work. We could add "updates of mageia distribution building +</I>><i> > tools are allowed to ensure that packagers using stable releases have +</I>><i> > the same tools than those using cauldron" +</I>><i> +</I>><i> Personally, I would prefer that we first refine the policy and then act +</I>><i> rather than the contrary :) +</I>><i> +</I> +Indeed :) + +><i> And so, if we provides newer version of tools, what is wrong with using +</I>><i> backports for that ? +</I>><i> +</I>><i> I am not keen on pushing our newer tool on update, since we plan to have +</I>><i> our server using mageia, and so in the futur, if we push newer iurt, +</I>><i> mgarepo, rpmlint, they may potentially disrupt build system. So by being +</I>><i> clear and using backports, we would avoid such problem more easily. +</I> +Except if you plan to use those newer version on the build system, in which +case sending to updates_testing to have them well tested then pushed to +updates would avoid having to install backports on the BS ? + +Samuel +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="006719.html">[Mageia-dev] new mgarepo version +</A></li> + <LI>Next message: <A HREF="006734.html">[Mageia-dev] new mgarepo version +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6722">[ date ]</a> + <a href="thread.html#6722">[ thread ]</a> + <a href="subject.html#6722">[ subject ]</a> + <a href="author.html#6722">[ 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> |