<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Backports policy clarification (and discussion)
</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%20clarification%20%28and%20discussion%29&In-Reply-To=%3C1596635.BOdpOEhydj%40localhost%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="016295.html">
<LINK REL="Next" HREF="016272.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Backports policy clarification (and discussion)</H1>
<B>AL13N</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20policy%20clarification%20%28and%20discussion%29&In-Reply-To=%3C1596635.BOdpOEhydj%40localhost%3E"
TITLE="[Mageia-dev] Backports policy clarification (and discussion)">alien at rmail.be
</A><BR>
<I>Fri Jun 8 21:07:11 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="016295.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
<LI>Next message: <A HREF="016272.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16302">[ date ]</a>
<a href="thread.html#16302">[ thread ]</a>
<a href="subject.html#16302">[ subject ]</a>
<a href="author.html#16302">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Op vrijdag 8 juni 2012 19:56:52 schreef Samuel Verschelde:
><i> Le vendredi 8 juin 2012 19:35:28, Sander Lepik a écrit :
</I>><i> > I don't think that we need to support backports that much. It should be
</I>><i> > clear that backports might not get all security updates. We should
</I>><i> > guarantee that it's possible to upgrade to next stable release and that's
</I>><i> > about it. We really don't have resources for more.
</I>><i>
</I>><i> That backports are supported is the key point of the policy, which was
</I>><i> discussed and validated months ago. It's not a "let's throw in random
</I>><i> packages" media, it's part of the distribution. Resources will limit the
</I>><i> number of different packages we are able to backport AND maintain, not the
</I>><i> quality of our support.
</I>><i>
</I>><i> So I'd like us to discuss the way to attain this objective rather than try
</I>><i> to force users needs to fit with what's simpler for us. Solutions probably
</I>><i> revolve around taking backports into account during upgrade, which is
</I>><i> doable. Hard, maybe, but doable:
</I>><i> - online upgrade can use backports media for packages not coming from
</I>><i> release. If we don't know where a package comes from we can start storing
</I>><i> that information somewhere, or guess (any package with higher version
</I>><i> installed than that in target distro's updates should be updated using
</I>><i> backports media). - DVD could detect packages which can't be updated (in
</I>><i> fact, it should do it already since there are already, DVDs having limited
</I>><i> space), and warn about them. DVD upgrade should also, if possible, detect
</I>><i> dependency problems *before* actually upgrading. Then if network is
</I>><i> available ask the user if they want to use online media for safer upgrade.
</I>><i>
</I>><i> Samuel
</I>
sounds like someone wants to make a Feature wiki page
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="016295.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
<LI>Next message: <A HREF="016272.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16302">[ date ]</a>
<a href="thread.html#16302">[ thread ]</a>
<a href="subject.html#16302">[ subject ]</a>
<a href="author.html#16302">[ 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>