diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101009/001050.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101009/001050.html | 109 |
1 files changed, 109 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101009/001050.html b/zarb-ml/mageia-dev/20101009/001050.html new file mode 100644 index 000000000..f060b4a48 --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/001050.html @@ -0,0 +1,109 @@ +<!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=%3C4CAFE54C.2030501%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001049.html"> + <LINK REL="Next" HREF="001051.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>andré</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=%3C4CAFE54C.2030501%40laposte.net%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">andr55 at laposte.net + </A><BR> + <I>Sat Oct 9 05:45:16 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001049.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001051.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1050">[ date ]</a> + <a href="thread.html#1050">[ thread ]</a> + <a href="subject.html#1050">[ subject ]</a> + <a href="author.html#1050">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Frank Griffin a écrit : +><i> Marc Paré wrote: +</I>><i> +</I>>><i> Thanks. So this thread is to see if there were a possibility to +</I>>><i> programme a more efficient roll-back option so that it would be more +</I>>><i> "aware" of the previous "dependencies" needs for the previous version. +</I>>><i> Having "double dependencies" is not so much of a problem, it is the +</I>>><i> rollback to a previous version where the dependency confusion may +</I>>><i> occur, and, ONLY, if an upgraded type of "dependency" thread had been +</I>>><i> installed. (Sorry I may have used the wrong terms in the last sentence). +</I>>><i> +</I>><i> Well, sort of. It's not an issue of efficiency, but of convenience and +</I>><i> just making it possible to do without resorting to manual use of the rpm +</I>><i> command. +</I>><i> +</I>><i> The rpm command "knows" that a new version replacing the old version +</I>><i> supplies the same things that the old one did, so it will quietly allow +</I>><i> the upgrade. It will also do what we need, i.e. go the other way and +</I>><i> replace a newer version with an older one if you use the --oldpackage +</I>><i> keyword. We just need urpmi to support its use +</I> +One thing that could facilitate this process, if the computer has a lot +of free disk space, is to rename the files being removed (copying the +configuration files), instead of erasing them. Although they will +probably have to be erased eventually, since no computer has unlimited +disk space. Keeping them long enough that a roll-back is no longer +probable could be workable. +Then a roll-back could be done very quickly, since the files are already +on disk, and presumably reliably. Of course, if new data has been +entered, and the format has been changed, this could be problematic. +Note that configuration files that have been changed from the +installation default are often already saved. (Generally ".old" is +appended to the configuration file name, sometimes ".new" to the new +configuration file.) +This of course adds the maintenance task of removing the old files at +some point - it could be done automatically according to some criteria, +or the user could have to do it manually, perhaps after being prompted +about it. + +(This rollback capability occurs with Microsoft products. The saved +files are only removed manually, on user initiative, which partly +explains the bloated size of a Microsoft installation over time.) + +If renaming-instead-of-deleting is implemented, perhaps a "do not keep +old program files (useful if limited disk space)" checkbox option would +be useful for computers with less free disk space. +Of course how much disk space is usable to save old programs on a +computer depends on the disk space usage for other purposes over time. + +my 2 cents :) + +- André (andre999) + +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001049.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001051.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1050">[ date ]</a> + <a href="thread.html#1050">[ thread ]</a> + <a href="subject.html#1050">[ subject ]</a> + <a href="author.html#1050">[ 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> |