diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101006/000876.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101006/000876.html | 150 |
1 files changed, 150 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101006/000876.html b/zarb-ml/mageia-dev/20101006/000876.html new file mode 100644 index 000000000..243789133 --- /dev/null +++ b/zarb-ml/mageia-dev/20101006/000876.html @@ -0,0 +1,150 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Various proposals around backports and other media management + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Various%20proposals%20around%20backports%20and%20other%20media%0A%09management&In-Reply-To=%3C201010052306.41676.bgmilne%40multilinks.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + + <LINK REL="Next" HREF="000880.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Various proposals around backports and other media management</H1> + <B>Buchan Milne</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Various%20proposals%20around%20backports%20and%20other%20media%0A%09management&In-Reply-To=%3C201010052306.41676.bgmilne%40multilinks.com%3E" + TITLE="[Mageia-dev] Various proposals around backports and other media management">bgmilne at multilinks.com + </A><BR> + <I>Wed Oct 6 00:06:41 CEST 2010</I> + <P><UL> + + <LI>Next message: <A HREF="000880.html">[Mageia-dev] Various proposals around backports and other media management +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#876">[ date ]</a> + <a href="thread.html#876">[ thread ]</a> + <a href="subject.html#876">[ subject ]</a> + <a href="author.html#876">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Tuesday, 5 October 2010 19:46:45 Samuel Verschelde wrote: +><i> Hello to everyone on the list, +</I>><i> +</I>><i> As some people said in another thread, Mandriva's current media schema +</I>><i> already gives the opportunity to : - install newer versions of software if +</I>><i> needed (from backports media), - keep a stable system with only security +</I>><i> fixes if needed (updates media, for servers or any workstation where +</I>><i> stability counts more than being bleeding-edge) +</I>><i> +</I>><i> However, we can improve things around backports, updates, testing and debug +</I>><i> media for the end user's benefit. +</I>><i> +</I>><i> I'd like to propose the following improvements if you think they would be +</I>><i> good (and I'm ready to help make them happen) : +</I>><i> +</I>><i> +</I>><i> - a section on the mageia website dedicated to package updates : what's new +</I>><i> in security/bugfix updates, what's new in backports (aka version updates), +</I>><i> ... with screen captures, description of what changed in this version, +</I>><i> links to upstream websites, comments from users, focus on some +</I>><i> applications... +</I> +Please take into consideration features that might be beneficial to package +maintainers as well. If you haven't yet, please look at e.g. Youri project, +Sophie etc. + +><i> Some user communities already did that for 3rd party +</I>><i> repositories for Mandriva, and having it in a centralized and visible +</I>><i> place would make backports more visible. How many users know that latest +</I>><i> versions for wine, wesnoth (one of the best opensource games), vlc, and +</I>><i> many other packages are already available in backports media for mandriva +</I>><i> ? Today there is a changelog mailing list, but this is not for everyone. +</I>><i> This would be more user-centric than packager-centric. I tried to improve +</I>><i> backports visibility on the Mandriva forum, but without any automation it +</I>><i> took an enormous amount of time to maintain : +</I>><i> <A HREF="http://forum.mandriva.com/viewforum.php?f=123">http://forum.mandriva.com/viewforum.php?f=123</A> (see threads beginning with +</I>><i> "New Soft" or "Backport") +</I> +RSS feed or use of twitter by build system may be useful .... + + +><i> - add a "welcome" screen to rpmdrake, where people could choose between : +</I>><i> * Browse and install security / bugfix updates +</I>><i> * Browse and install new versions of software ("backports") +</I>><i> * Install new software +</I>><i> * Uninstall software +</I>><i> * Skip this newbie step and get me to the real stuff, I'll use the various +</I>><i> options to do what I need Rpmdrake can also be enhanced to show for each +</I>><i> package update whether it's a backport or a standard update. It's not easy +</I>><i> currently (you have to dig into package details). +</I> +I would like a column for 'medium name' or so, which you could sort on ... + +><i> - (the biggest part, but the one with most long term benefits I hope) add +</I>><i> metadata to media to make urpmi more media-aware. Today, rpmdrake detects +</I>><i> backports because the backports media have "backports" in their name. +</I>><i> That's a (useful) hack, but we could do better. One solution could be to +</I>><i> give metadata to each media : * release vs updates vs backports +</I>><i> * testing vs stable +</I>><i> * debug vs non-debug +</I>><i> Combination of these "tags" would give the following media : +</I>><i> * main release (just like today's media) +</I>><i> * main updates +</I>><i> * main updates testing : for update candidates, this is our current +</I>><i> "main testing" media * main backports +</I>><i> * main backports testing : for backports candidates (as someone who +</I>><i> frequently does backports, I sometimes feel the lack for it) +</I> +As long as it doesn't take the focus off the development release. In Mandriva, +I think there were some uploads to backports before the upload to cooker, +which can cause problems for users if not corrected. + +><i> * main +</I>><i> release debug... +</I>><i> * contrib... +</I>><i> * non-free... +</I>><i> It may seem a lot of media, but in fact you have to think they all are only +</I>><i> flavours of the main, contrib, non-free, and other media. We can think of +</I>><i> a better presentation in UI tools that will in fact make them appear less +</I>><i> cluttered than it is today : +</I>><i> <A HREF="http://stormi.lautre.net/fichiers/mageia/media-configuration-proposal.ods">http://stormi.lautre.net/fichiers/mageia/media-configuration-proposal.ods</A> +</I>><i> +</I>><i> In CLI, urpmi would default to using only release and updates media (which +</I>><i> you could change in configuration if needed), and you could use other +</I>><i> media with the following switches for example : --use-backports : enables +</I>><i> all backports media +</I>><i> --use-testing : enables all testing media +</I>><i> --use-debug : enables all debug media +</I> +Well, using the 'name hack', for some time (since 2009.1?), users who have +"default" repos should currently be able to use '--searchmedia Backports', '-- +searchmedia Testing', '--searchmedia Debug' for the same purpose. (May require +urpmi.update of the medium first). + +Regards, +Buchan +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + + <LI>Next message: <A HREF="000880.html">[Mageia-dev] Various proposals around backports and other media management +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#876">[ date ]</a> + <a href="thread.html#876">[ thread ]</a> + <a href="subject.html#876">[ subject ]</a> + <a href="author.html#876">[ 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> |