diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101009/001062.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101009/001062.html | 109 |
1 files changed, 109 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101009/001062.html b/zarb-ml/mageia-dev/20101009/001062.html new file mode 100644 index 000000000..ba1e991e4 --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/001062.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=%3C4CB07220.2060404%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001060.html"> + <LINK REL="Next" HREF="001069.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=%3C4CB07220.2060404%40laposte.net%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">andr55 at laposte.net + </A><BR> + <I>Sat Oct 9 15:46:08 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001060.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001069.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1062">[ date ]</a> + <a href="thread.html#1062">[ thread ]</a> + <a href="subject.html#1062">[ subject ]</a> + <a href="author.html#1062">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Luca Berra a écrit : +><i> +</I>><i> On Sat, Oct 09, 2010 at 11:10:36AM +0200, Renaud MICHEL wrote: +</I>>><i> On samedi 09 octobre 2010 at 05:45, andré wrote : +</I>>>><i> Note that configuration files that have been changed from the +</I>>>><i> installation default are often already saved. (Generally ".old" is +</I>>>><i> appended to the configuration file name, sometimes ".new" to the new +</I>>>><i> configuration file.) +</I>>><i> +</I>>><i> But here you are only talking about system-wide configuration files, +</I>>><i> which are known of rpm as they are part of the package and marked as +</I>>><i> config files. +</I>>><i> But what about user specific configuration files? +</I>>><i> For the easy kind, where a program will have a single configuration +</I>>><i> file (or dedicated directory), a pre-inst script could find it in the +</I>>><i> home of each users and backup them. But you have cases of programs +</I>>><i> which have configuration scattered in multiple shared directories +</I>>><i> (like KDE), or even non-deterministic configuration files and it can +</I>>><i> become very tricky to find all the files to backup. +</I>>><i> And you have the really hard kind, where the same configuration file +</I>>><i> may be shared by different packages. For example, plasma applet +</I>>><i> configurations are stored in a few ~/.kde4/share/config/plasma* files. +</I>Good point. So user-specific configuration files would have to be taken +into account. +BTW, there is a similar complication for some Gnome packages. +So it would take a lot more time and effort to accommodate such rollbacks. +However most packages would be much simpler to reliably roll back. +So it seems useful that packages be marked as suitable for rollback (or +not). +><i> +1 +</I>><i> this is the very problem why i believe rollbacks are not that easy +</I>><i> +</I>Because the rollback will be automatic and must be very reliable, it is +not something to be taken lightly. A malfunctioning rollback would be +considerably worse than the current manual rollback process. + +Note that insisting that all backports depend on the same versions of +required packages as the distro release for which the backport is made +will considerably reduce one potential source of problems. As well, if +a new version of a particular application has important format changes, +perhaps there should be a policy of not making backports for it. +So candidates for rollbacks would be mostly restricted to applications +developped and tested for the current release of the distro. +Thus the utility of automated rollbacks would be considerably reduced. + +Another 2 cents :) + +- André (andre999) +</PRE> + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001060.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001069.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1062">[ date ]</a> + <a href="thread.html#1062">[ thread ]</a> + <a href="subject.html#1062">[ subject ]</a> + <a href="author.html#1062">[ 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> |