diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-June/016911.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-June/016911.html | 143 |
1 files changed, 143 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016911.html b/zarb-ml/mageia-dev/2012-June/016911.html new file mode 100644 index 000000000..fc126efba --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016911.html @@ -0,0 +1,143 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Backports Summary + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20Summary&In-Reply-To=%3C5132624.7yP981pG2k%40tech009%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="016869.html"> + <LINK REL="Next" HREF="017057.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Backports Summary</H1> + <B>Samuel Verschelde</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20Summary&In-Reply-To=%3C5132624.7yP981pG2k%40tech009%3E" + TITLE="[Mageia-dev] Backports Summary">stormi at laposte.net + </A><BR> + <I>Wed Jun 27 13:51:38 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="016869.html">[Mageia-dev] Backports Summary +</A></li> + <LI>Next message: <A HREF="017057.html">[Mageia-dev] Backports Summary +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16911">[ date ]</a> + <a href="thread.html#16911">[ thread ]</a> + <a href="subject.html#16911">[ subject ]</a> + <a href="author.html#16911">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le mardi 26 juin 2012 22:25:10 Thomas Backlund a écrit : +><i> And since we can continue this what/if discussion forever, +</I>><i> and thereby delay backports even more here is my take on it: +</I>><i> +</I>><i> my suggestions to decide on question 1 and 2: +</I>><i> 1. backporting bigger version to mga1 than mga2 has is +</I>><i> allowed as it will otherwise restrict backporting +</I>><i> too much. (and since its leaf packages, it should +</I>><i> not break (too much)). Lets just make it clear to +</I>><i> everyone using backports. +</I> +Ok for me, but would be better if before upgrade a warning is raised because +of backports that cannot be updated and could possibily prevent the upgrade of +other packages. + +><i> +</I>><i> 2. we cant really require that as the one backporting +</I>><i> the package to mga1 has to backport it to mga2 too +</I>><i> as he/she might not be using mga2 at all. if someone +</I>><i> wants/needs the backport for mga2, they need to +</I>><i> request that. (in reality, going by how backports +</I>><i> got handled in mdv most backports will end up in +</I>><i> all supported releases anyway) +</I> +Thinking of when upgrade tools will allow to take backports into account for +upgrade, I'd rather require that packages be backported to both mga2 and mga1 +so that upgrade always works, but until then if people prefer your option I +won't speak against. + +Ok, and people join QA to test backports if you really want them ! :) + +Samuel +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="016869.html">[Mageia-dev] Backports Summary +</A></li> + <LI>Next message: <A HREF="017057.html">[Mageia-dev] Backports Summary +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16911">[ date ]</a> + <a href="thread.html#16911">[ thread ]</a> + <a href="subject.html#16911">[ subject ]</a> + <a href="author.html#16911">[ 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> |