diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/2012-June/016515.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/2012-June/016515.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-June/016515.html | 135 |
1 files changed, 135 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016515.html b/zarb-ml/mageia-dev/2012-June/016515.html new file mode 100644 index 000000000..fd0b275da --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016515.html @@ -0,0 +1,135 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposed Feature:Backports_update_applet + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposed%20Feature%3ABackports_update_applet&In-Reply-To=%3C4FDAC308.8040109%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="016514.html"> + <LINK REL="Next" HREF="016516.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposed Feature:Backports_update_applet</H1> + <B>andre999</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposed%20Feature%3ABackports_update_applet&In-Reply-To=%3C4FDAC308.8040109%40laposte.net%3E" + TITLE="[Mageia-dev] Proposed Feature:Backports_update_applet">andre999mga at laposte.net + </A><BR> + <I>Fri Jun 15 07:07:20 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="016514.html">[Mageia-dev] Proposed Feature:Backports_update_applet +</A></li> + <LI>Next message: <A HREF="016516.html">[Mageia-dev] Proposed Feature:Backports_update_applet +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16515">[ date ]</a> + <a href="thread.html#16515">[ thread ]</a> + <a href="subject.html#16515">[ subject ]</a> + <a href="author.html#16515">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>blind Pete a écrit : +><i> andre999 wrote: +</I>><i> +</I>><i> +</I>>><i> blind Pete a écrit : +</I>>><i> +</I>>>><i> andre999 wrote: +</I>>>><i> +</I>>>><i> +</I>>>><i> +</I>>>>><i> blind Pete a écrit : +</I>>>>><i> +</I>>>>><i> +</I>>>>>><i> Samuel Verschelde wrote: +</I>>>>>><i> +</I>>>>>><i> +</I>>>>>><i> +</I>>>>>><i> +</I>>><i> +</I>><i> [snip] +</I>><i> +</I>>>>><i> - Functioning as an update, it would only replace already installed +</I>>>>><i> backports, once the tools are appropriately adjusted. +</I>>>>><i> +</I>>>>><i> +</I>>>><i> There are a couple of ways to do that. The simplest that I can think +</I>>>><i> of is to split "backports" into "backports" and "backports update". +</I>>>><i> Allow cherry picking from "backports" and apply "backports update" +</I>>>><i> automatically. +</I>>>><i> +</I>>>><i> +</I>>><i> I was thinking of cases where the user chooses to "update" their +</I>>><i> system. New versions of backports already installed would be presented +</I>>><i> as updates, along with those from the update repos. +</I>>><i> Just as we don't have any update-update repos, it wouldn't make sense to +</I>>><i> have backport-update repos either. +</I>>><i> +</I>><i> [snip] +</I>><i> +</I>><i> It depends on how you look at it. +</I>><i> +</I>><i> If you consider non-free, tainted, and backport to be optional +</I>><i> and any update package to be highly recommended if and only if +</I>><i> the corresponding package is already installed. Then is does +</I>><i> not matter if the old package is a tainted.rpm, nonfree.rpm, +</I>><i> bp.rpm, or an ordinary rpm. Just one way to look at it, not +</I>><i> the only way. +</I>><i> +</I>><i> +</I>But how is it possible to distinguish a priori between a backport which +will be an update and one which will be a "new" backport on a users' +system. It would only be an "update" if the user has already installed +the corresponding backport on their system. +If the fact it is a backport is ignored, then every backport would be, +by definition, an update. Even packages newly imported to Mageia. + +To me, a "corresponding" package is one from the same category, +according to whether is is backport or not, and according to whether in +"core", "nonfree", or "tainted". +To consider otherwise is to deny the importance of these categories. + +Backports are considered separately because they are much more at risk +to not function properly, since they weren't tested with the rest of the +release, being added afterwards. So we have to be much more careful +about adding them. The last thing we want is for the backports to be +included automatically with updates, even if the user had not already +decided to install the corresponding backport. Installing a backport +should be an exceptional, explicitly decided activity -- except when the +user has already decided to install the corresponding backport, when it +is useful to present newer versions as updates. They are likely +security or bug fixes. + +-- +André + +</PRE> + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="016514.html">[Mageia-dev] Proposed Feature:Backports_update_applet +</A></li> + <LI>Next message: <A HREF="016516.html">[Mageia-dev] Proposed Feature:Backports_update_applet +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16515">[ date ]</a> + <a href="thread.html#16515">[ thread ]</a> + <a href="subject.html#16515">[ subject ]</a> + <a href="author.html#16515">[ 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> |