diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101008/001038.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101008/001038.html | 114 |
1 files changed, 114 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101008/001038.html b/zarb-ml/mageia-dev/20101008/001038.html new file mode 100644 index 000000000..5c73c521e --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001038.html @@ -0,0 +1,114 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3Ci8npuf%24c8u%241%40dough.gmane.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001032.html"> + <LINK REL="Next" HREF="001042.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Marc Paré</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3Ci8npuf%24c8u%241%40dough.gmane.org%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">marc at marcpare.com + </A><BR> + <I>Fri Oct 8 21:03:42 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001032.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001042.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1038">[ date ]</a> + <a href="thread.html#1038">[ thread ]</a> + <a href="subject.html#1038">[ subject ]</a> + <a href="author.html#1038">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le 2010-10-08 13:49, Frank Griffin a écrit : +><i> Marc Paré wrote: +</I>>><i> +</I>>><i> +</I>>><i> As it seems we keep going in circles on this Romain has arranged the +</I>>><i> following so that the threads on this topic become more focussed: +</I>><i> I'd read the thread previously, and checked the wiki page, but this is a +</I>><i> different issue. That wiki page is pretty much just a poll (who are +</I>><i> you, what do you do with your systems, what kind of release schedule do +</I>><i> you want). This proposal is independent of whether there's a rolling +</I>><i> release or not; it's about presenting the update process to the user in +</I>><i> a different way. +</I>><i> +</I> +Yup, I reread your proposal. You are right. It would be nice for you to +add it to the wiki page. This is after all, as you said, one of the +issues raised in the thread. + +-------------------- + +As to your proposal, the issue with "Backports" and lack of +understanding form the users point of view is quite a large one. There +should be a VERY descriptive info section explaining the purpose of +"Backports". The lack of a descriptive expanation just did not make the +"Backports" section of the MCC popular by users. We just assumed that +when a newer version of our favourite soft. had come out, that all we +had to do is wait for it to come up in the "you know, that red ball +thingy in the tasbar on the right-bottom". + +I am now making use of Backports and loving it! But also realize the +dangers of using it. + +-------------------- + +So, as to your proposal, I am in agreement with it. Maybe a suggestion +(more of a question), seeing as the issues have to deal more with the +dependencies of a "roll-back", what if, "Backports" would install, +somehow the software updates in a self compartment kind of way (sorry my +language terms may not be descriptive enough). + +Users know that repositories are activated and some are not at the time +of install. I think that most users have a faint idea of this. But if +Backports were to be used more at the user level, what is clear, is +that, there should be a roll-back feature. If the roll-back feature, as +a normal course of rolling-back will or could remove other softs due to +dependencies, then maybe possible option would be to have the "Backport" +software installations install all dependencies in such a way as to +isolate them from the larger distro packages. This would in effect could +make a secondary related-dependency file on the system. Then if a +roll-back were done a Backported software package only the associated +dependencies would be deleted. + +Could this be done? + +Sorry, I am not sure if this is written clearly enough. + +Marc + +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001032.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001042.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1038">[ date ]</a> + <a href="thread.html#1038">[ thread ]</a> + <a href="subject.html#1038">[ subject ]</a> + <a href="author.html#1038">[ 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> |