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-discuss/20101107/002956.html | 72 +++++++++++++++++++++++++++++ 1 file changed, 72 insertions(+) create mode 100644 zarb-ml/mageia-discuss/20101107/002956.html (limited to 'zarb-ml/mageia-discuss/20101107/002956.html') diff --git a/zarb-ml/mageia-discuss/20101107/002956.html b/zarb-ml/mageia-discuss/20101107/002956.html new file mode 100644 index 000000000..57bfa51f8 --- /dev/null +++ b/zarb-ml/mageia-discuss/20101107/002956.html @@ -0,0 +1,72 @@ + + + + [Mageia-discuss] Suggestions for the ISO + + + + + + + + + +

[Mageia-discuss] Suggestions for the ISO

+ Renaud MICHEL + r.h.michel+mageia at gmail.com +
+ Sun Nov 7 23:43:46 CET 2010 +

+
+ +
On dimanche 07 novembre 2010 at 22:33, Luca Berra wrote :
+> > you must include all intermediate updates packages to create the delta.
+> 
+> you just have to keep track of package 1 and n-1, not all of them
+
+No, because a roll back of a file can happen on any update. If a file is 
+changed in release n-2 and rolled back in n-1, if you only consider packages 
+1 n-1 and n you miss the roll back for the people who updated to n-2 but 
+missed the update to n-1.
+So the system that will create the deltas must have access to every update 
+published since the release, or at least maintain a list of all the files 
+that changed in any update. And not only changes in the files themselves, 
+but also to their meta-informations, like ownership and mode, and other rpm-
+related meta-informations like %doc or %config.
+
+-- 
+Renaud Michel
+
+ + +
+

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