<!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=%3C2448482.6W11EcKTdv%40tech009%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="016921.html">
   <LINK REL="Next"  HREF="016926.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=%3C2448482.6W11EcKTdv%40tech009%3E"
       TITLE="[Mageia-dev] Backports Summary">stormi at laposte.net
       </A><BR>
    <I>Wed Jun 27 16:29:50 CEST 2012</I>
    <P><UL>
        <LI>Previous message: <A HREF="016921.html">[Mageia-dev] Backports Summary
</A></li>
        <LI>Next message: <A HREF="016926.html">[Mageia-dev] Backports Summary
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#16923">[ date ]</a>
              <a href="thread.html#16923">[ thread ]</a>
              <a href="subject.html#16923">[ subject ]</a>
              <a href="author.html#16923">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Le mercredi 27 juin 2012 16:08:10 nicolas vigier a &#233;crit :
&gt;<i> On Wed, 27 Jun 2012, andre999 wrote:
</I>&gt;<i> &gt;&gt;&gt; I would favour tagging backports as update repos, so that in the event
</I>&gt;<i> &gt;&gt;&gt; of a newer backport for security or bug fixes, that it will be
</I>&gt;<i> &gt;&gt;&gt; automatically presented with other updates.
</I>&gt;<i> &gt;&gt; 
</I>&gt;<i> &gt;&gt; No.
</I>&gt;<i> &gt;&gt; as the update applet currently works it would show the backport as
</I>&gt;<i> &gt;&gt; an update even if you dont have an earlier backport installed,
</I>&gt;<i> &gt;&gt; defeating the purpose of having separate /updates vs /backports
</I>&gt;<i> &gt; 
</I>&gt;<i> &gt; This is conditional on first modifying the update tools, as suggested
</I>&gt;<i> &gt; next.
</I>&gt;<i> &gt; A backport should only update an already installed backport.
</I>&gt;<i> &gt; (Similarly for nonfree and tainted, if that is not already the case.)
</I>&gt;<i> 
</I>&gt;<i> We should not change the behaviour of medias tagged as update repo. If
</I>&gt;<i> we want a different behaviour for backports then we should tag those
</I>&gt;<i> medias as backport, not update.
</I>
Fully agreed
</PRE>







































<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="016921.html">[Mageia-dev] Backports Summary
</A></li>
	<LI>Next message: <A HREF="016926.html">[Mageia-dev] Backports Summary
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#16923">[ date ]</a>
              <a href="thread.html#16923">[ thread ]</a>
              <a href="subject.html#16923">[ subject ]</a>
              <a href="author.html#16923">[ 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>