diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-June/016309.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-June/016309.html | 141 |
1 files changed, 141 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016309.html b/zarb-ml/mageia-dev/2012-June/016309.html new file mode 100644 index 000000000..afbd54fe7 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016309.html @@ -0,0 +1,141 @@ +<!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=%3Cvnpaa9-nm.ln1%40psd.motzarella.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="016280.html"> + <LINK REL="Next" HREF="016330.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposed Feature:Backports_update_applet</H1> + <B>blind Pete</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposed%20Feature%3ABackports_update_applet&In-Reply-To=%3Cvnpaa9-nm.ln1%40psd.motzarella.org%3E" + TITLE="[Mageia-dev] Proposed Feature:Backports_update_applet">0123peter at gmail.com + </A><BR> + <I>Sat Jun 9 04:41:34 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="016280.html">[Mageia-dev] Proposed Feature:Backports_update_applet +</A></li> + <LI>Next message: <A HREF="016330.html">[Mageia-dev] Proposed Feature:Backports_update_applet +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16309">[ date ]</a> + <a href="thread.html#16309">[ thread ]</a> + <a href="subject.html#16309">[ subject ]</a> + <a href="author.html#16309">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Samuel Verschelde wrote: + +><i> Following Backports opening due soon, and since our policy is that +</I>><i> backports are supported (security, bugfix), we need a way to push backport +</I>><i> updates for users who installed backports. Otherwise, we can't really say +</I>><i> that we're providing security updates to our backports. +</I>><i> +</I>><i> My feature proposal is to implement something similar to what mgaonline + +</I>><i> MageiaUpdate does for updates, but for backports, with some changes due to +</I>><i> the fact that users will rarely want that "all" packages on the system be +</I>><i> updated from backports when the backports media are activated. +</I>><i> +</I>><i> <A HREF="https://wiki.mageia.org/en/Feature:Backports_update_applet">https://wiki.mageia.org/en/Feature:Backports_update_applet</A> +</I>><i> +</I>><i> I don't think I can do the dev myself. I can work on more detailed +</I>><i> specifications with a developer though. +</I>><i> +</I>><i> Samuel +</I> +There are a multiple ways that this problem could be handled. +Yours is one. + +Samuel's way: + +Need "something" to know that a backport package +has been installed, to remember that fact, and to do an extra +backport update search when looking for updates. + +It would need to keep working if the user changed desktop +environments, or even stopped used a desktop and just used +the command line. Does mgaonline do this? There could be +room to improve that. + +If it can be detected that a backport package has been installed +(or less efficiently, detect that a backports repository +has been activated) set up a cron job (or reconfigure mgaonline) +and leave it like that for the life of the installation. + +Geeks way: + +Only use urpmi as a command line tool and edit urpmi.cfg with vi. + +When activating a backports repository mark it as an update +repository. Then update with "urpmi --excludemedia [backport media, ...]" +accepting all suggestions, followed by "urpmi --auto-select" +and look at what is offered before accepting. + +My suggestion: + +Add "bp" to the package name and have separate backports update +repositories. + +Users would then be able to cherry pick from backports and +updates should _just work_ without extra intervention. + +The only difficulty that I can think of is, when a backport +(or backport update) package is pushed to updates. It would +not be necessary to do a real update but the rpm database +should be updated such that version N-bp supersedes version N. +(And the N-bp packages should be removed from the repositories.) + +Can anyone see any holes in the logic? + +What would be easiest to implement? + +-- +blind Pete +Sig goes here... + +</PRE> + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="016280.html">[Mageia-dev] Proposed Feature:Backports_update_applet +</A></li> + <LI>Next message: <A HREF="016330.html">[Mageia-dev] Proposed Feature:Backports_update_applet +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16309">[ date ]</a> + <a href="thread.html#16309">[ thread ]</a> + <a href="subject.html#16309">[ subject ]</a> + <a href="author.html#16309">[ 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> |