summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20101008/001033.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/20101008/001033.html')
-rw-r--r--zarb-ml/mageia-dev/20101008/001033.html102
1 files changed, 102 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101008/001033.html b/zarb-ml/mageia-dev/20101008/001033.html
new file mode 100644
index 000000000..1062558ed
--- /dev/null
+++ b/zarb-ml/mageia-dev/20101008/001033.html
@@ -0,0 +1,102 @@
+<!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=%3C4CAF5C7C.5000605%40roadrunner.com%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="001026.html">
+ <LINK REL="Next" HREF="001044.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1>
+ <B>Frank Griffin</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=%3C4CAF5C7C.5000605%40roadrunner.com%3E"
+ TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">ftg at roadrunner.com
+ </A><BR>
+ <I>Fri Oct 8 20:01:32 CEST 2010</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="001026.html">[Mageia-dev] Proposal: Updating released versions (long post)
+</A></li>
+ <LI>Next message: <A HREF="001044.html">[Mageia-dev] Proposal: Updating released versions (long post)
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1033">[ date ]</a>
+ <a href="thread.html#1033">[ thread ]</a>
+ <a href="subject.html#1033">[ subject ]</a>
+ <a href="author.html#1033">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Luca Berra wrote:
+&gt;<i> On Thu, Oct 07, 2010 at 07:49:29PM -0400, Frank Griffin wrote:
+</I>&gt;&gt;<i> I'd like to propose the following model for updating released versions:
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> 1) Users should not have to see, except in minor ways, the different
+</I>&gt;&gt;<i> repositories. Urpmi may see them, and advanced or ideologically polar
+</I>&gt;&gt;<i> users may care about them (e.g. free vs non-free), but most users
+</I>&gt;<i> I object to this specific point, if what we are doing is free software
+</I>&gt;<i> that should be made clear to users. and i believe the user shold be
+</I>&gt;<i> asked wether they want to use only free software or not.
+</I>
+I have no objection to allowing users to check a box saying they want
+free or mixed systems. I just don't want them to have to mess with a
+repository to do it.
+
+&gt;<i> I just read it 3 times, and i still believe doing the above might
+</I>&gt;<i> prove to be a
+</I>&gt;<i> nightmare.
+</I>&gt;<i> rolling back a single, well identified change is a doable task.
+</I>&gt;<i> rolling back proceduraly a complex change becomes exponentially complex
+</I>&gt;<i> even for experienced system engineers, let alone a piece of software.
+</I>
+I agree that the work becomes exponentially complex, but not the concept
+of what has to be done. After all, what can be installed in an
+automated way can be uninstalled.
+
+In any case, I would think that the primary use of this facility would
+be to uninstall a single package. Urpme already knows how to do that,
+and (provided you have the older RPM around) urpmi knows how to install
+the old one. We expect users who want to roll back a package to do that
+manually today.
+
+The problem is that removing the new package, if it provides something
+that lots of things require, will want to uninstall a large number of
+packages uselessly, because it doesn't know that you're about to turn
+around and install something else that provides it. All I'm suggesting
+is that
+ (a) we make the older RPMs available somewhere
+ (b) we automate the process to save three manual steps, and
+ (c) we wrap them in an atomic transaction (or what looks like one to
+the user) to solve the problem above
+</PRE>
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="001026.html">[Mageia-dev] Proposal: Updating released versions (long post)
+</A></li>
+ <LI>Next message: <A HREF="001044.html">[Mageia-dev] Proposal: Updating released versions (long post)
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1033">[ date ]</a>
+ <a href="thread.html#1033">[ thread ]</a>
+ <a href="subject.html#1033">[ subject ]</a>
+ <a href="author.html#1033">[ 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>