diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/006082.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-June/006082.html | 88 |
1 files changed, 88 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/006082.html b/zarb-ml/mageia-dev/2011-June/006082.html new file mode 100644 index 000000000..2ca47615d --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/006082.html @@ -0,0 +1,88 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal of a backporting process + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20of%20a%20backporting%20process&In-Reply-To=%3C201106280925.31714.anaselli%40linux.it%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="006040.html"> + <LINK REL="Next" HREF="006103.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal of a backporting process</H1> + <B>Angelo Naselli</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20of%20a%20backporting%20process&In-Reply-To=%3C201106280925.31714.anaselli%40linux.it%3E" + TITLE="[Mageia-dev] Proposal of a backporting process">anaselli at linux.it + </A><BR> + <I>Tue Jun 28 09:25:28 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="006040.html">[Mageia-dev] Proposal of a backporting process +</A></li> + <LI>Next message: <A HREF="006103.html">[Mageia-dev] Proposal of a backporting process +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6082">[ date ]</a> + <a href="thread.html#6082">[ thread ]</a> + <a href="subject.html#6082">[ subject ]</a> + <a href="author.html#6082">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>domenica 26 giugno 2011 alle 13:38, Michael Scherer ha scritto: +><i> See the thread about policy, and the part about "only packages that +</I>><i> nothing requires should be backported". +</I>I can't see very well the leaf story... I mean any packages +require something at least to build. Scripts need interpreters, so +i'd expect interpreters cannot be backported, but we can find a +script based package (using perl, ruby or python...) needing some other +script based one, the same could happen for programs. Now what can +we backport there? +A and B are leaves (?) but B uses A so i can revert A for a problem, +now are we sure A on stable works with B on backports? + +Morever we could not backport new major libraries, they would not conflicts +with stable though, but sure they could affect some packages built in backports +after that should not work without new major..... + +I'm confused :/ + +IMO we should improve the QA (or what else) and testing to allow a safe +installation and proving that will be upgraded to the next mageia release, +then if we call it backports, upgrades, updates or... that's +another and maybe less important thing. + +Angelo +-------------- next part -------------- +A non-text attachment was scrubbed... +Name: not available +Type: application/pgp-signature +Size: 198 bytes +Desc: This is a digitally signed message part. +URL: </pipermail/mageia-dev/attachments/20110628/39966419/attachment.asc> +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="006040.html">[Mageia-dev] Proposal of a backporting process +</A></li> + <LI>Next message: <A HREF="006103.html">[Mageia-dev] Proposal of a backporting process +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6082">[ date ]</a> + <a href="thread.html#6082">[ thread ]</a> + <a href="subject.html#6082">[ subject ]</a> + <a href="author.html#6082">[ 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> |