diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-June/016926.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-June/016926.html | 125 |
1 files changed, 125 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016926.html b/zarb-ml/mageia-dev/2012-June/016926.html new file mode 100644 index 000000000..1262dae53 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016926.html @@ -0,0 +1,125 @@ +<!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=%3C4FEB1CE7.9020708%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="016923.html"> + <LINK REL="Next" HREF="016929.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Backports Summary</H1> + <B>andre999</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20Summary&In-Reply-To=%3C4FEB1CE7.9020708%40laposte.net%3E" + TITLE="[Mageia-dev] Backports Summary">andre999mga at laposte.net + </A><BR> + <I>Wed Jun 27 16:47:03 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="016923.html">[Mageia-dev] Backports Summary +</A></li> + <LI>Next message: <A HREF="016929.html">[Mageia-dev] Backports Summary +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16926">[ date ]</a> + <a href="thread.html#16926">[ thread ]</a> + <a href="subject.html#16926">[ subject ]</a> + <a href="author.html#16926">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>nicolas vigier a écrit : +><i> On Wed, 27 Jun 2012, andre999 wrote: +</I>><i> +</I>><i> +</I>>>>><i> I would favour tagging backports as update repos, so that in the event +</I>>>>><i> of a newer backport for security or bug fixes, that it will be +</I>>>>><i> automatically presented with other updates. +</I>>>>><i> +</I>>>><i> No. +</I>>>><i> as the update applet currently works it would show the backport as +</I>>>><i> an update even if you dont have an earlier backport installed, +</I>>>><i> defeating the purpose of having separate /updates vs /backports +</I>>>><i> +</I>>><i> This is conditional on first modifying the update tools, as suggested next. +</I>>><i> A backport should only update an already installed backport. +</I>>><i> (Similarly for nonfree and tainted, if that is not already the case.) +</I>>><i> +</I>><i> We should not change the behaviour of medias tagged as update repo. If +</I>><i> we want a different behaviour for backports then we should tag those +</I>><i> medias as backport, not update. +</I>><i> +</I> +The idea is, once the tools are appropriately adjusted, to tag the +backport repos as update media, as in rpmdrake. But alternately we +could get the update tools to automatically treat backport repos as +update media for backports. +The concept is that backports would be presented for update along with +other updates. Backport updates would only replace backports, but +backports could be replaced by regular updates, if the version is equal +or higher. + +-- +André + +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="016923.html">[Mageia-dev] Backports Summary +</A></li> + <LI>Next message: <A HREF="016929.html">[Mageia-dev] Backports Summary +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16926">[ date ]</a> + <a href="thread.html#16926">[ thread ]</a> + <a href="subject.html#16926">[ subject ]</a> + <a href="author.html#16926">[ 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> |