From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/20101009/001069.html | 77 +++++++++++++++++++++++++++++++++ 1 file changed, 77 insertions(+) create mode 100644 zarb-ml/mageia-dev/20101009/001069.html (limited to 'zarb-ml/mageia-dev/20101009/001069.html') diff --git a/zarb-ml/mageia-dev/20101009/001069.html b/zarb-ml/mageia-dev/20101009/001069.html new file mode 100644 index 000000000..eb29fe6ca --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/001069.html @@ -0,0 +1,77 @@ + + + + [Mageia-dev] Proposal: Updating released versions (long post) + + + + + + + + + +

[Mageia-dev] Proposal: Updating released versions (long post)

+ Frank Griffin + ftg at roadrunner.com +
+ Sat Oct 9 22:10:51 CEST 2010 +

+
+ +
Luca Berra wrote:
+> On Sat, Oct 09, 2010 at 11:10:36AM +0200, Renaud MICHEL wrote:
+>>
+>> But here you are only talking about system-wide configuration files,
+>> which are known of rpm as they are part of the package and marked as
+>> config files.
+>> But what about user specific configuration files?
+>
+> +1
+> this is the very problem why i believe rollbacks are not that easy
+>
+The proposal included a recommendation for this, having the package
+scripts do the equivalent of an "rpmnew"/"rpmold", but with
+package-specific names.  Note that in a rollback, any changes made to
+the newer file would be lost, but that's unavoidable in any case since
+they may not be supported by the old format.
+
+Fortunately, the number of packages that do this reformatting is
+relatively small, and some of them (like NetBeans) create the newer
+versions in new-release-specific subdirectories, leaving the old ones
+intact.
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1