zarb-ml/mageia-discuss/20101108/002958.html


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-discuss] Suggestions for the ISO
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Suggestions%20for%20the%20ISO&In-Reply-To=%3C4CD7730B.7080900%40laposte.net%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="002957.html">
   <LINK REL="Next"  HREF="002959.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-discuss] Suggestions for the ISO</H1>
    <B>andre999</B> 
    <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Suggestions%20for%20the%20ISO&In-Reply-To=%3C4CD7730B.7080900%40laposte.net%3E"
       TITLE="[Mageia-discuss] Suggestions for the ISO">andr55 at laposte.net
       </A><BR>
    <I>Mon Nov  8 04:48:27 CET 2010</I>
    <P><UL>
        <LI>Previous message: <A HREF="002957.html">[Mageia-discuss] Suggestions for the ISO
</A></li>
        <LI>Next message: <A HREF="002959.html">[Mageia-discuss] [OT] KDE 4.5.2 for Mandrive
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#2958">[ date ]</a>
              <a href="thread.html#2958">[ thread ]</a>
              <a href="subject.html#2958">[ subject ]</a>
              <a href="author.html#2958">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Renaud MICHEL a &#233;crit :
&gt;<i> On dimanche 07 novembre 2010 at 22:33, Luca Berra wrote :
</I>&gt;<i>    
</I>&gt;&gt;&gt;<i> you must include all intermediate updates packages to create the delta.
</I>&gt;&gt;&gt;<i>        
</I>&gt;&gt;<i> you just have to keep track of package 1 and n-1, not all of them
</I>&gt;&gt;<i>      
</I>&gt;<i> No, because a roll back of a file can happen on any update. If a file is
</I>&gt;<i> changed in release n-2 and rolled back in n-1, if you only consider packages
</I>&gt;<i> 1 n-1 and n you miss the roll back for the people who updated to n-2 but
</I>&gt;<i> missed the update to n-1.
</I>&gt;<i> So the system that will create the deltas must have access to every update
</I>&gt;<i> published since the release, or at least maintain a list of all the files
</I>&gt;<i> that changed in any update. And not only changes in the files themselves,
</I>&gt;<i> but also to their meta-informations, like ownership and mode, and other rpm-
</I>&gt;<i> related meta-informations like %doc or %config.
</I>&gt;<i>    
</I>
You would have to keep the current version of all contained files that 
changed since the release version, even if reverted to the state of the 
release package.
As well, in the spec file, you would have to keep meta info on all the 
files that changed, including the files that were replaced, for each update.
This since some users might go from update -2 to update -5, for example.

If a user were to revert to a previous update, in most cases they would 
require either a full update or the release package + the delta update.  
This of course occurs much less frequently.
Note that if the user installed from ISO, they would likely have the 
release package readily available.

It might be possible to avoid including some meta info, by analysing 
which versions of the contained files are more recent, but because there 
are differing ways of representing versions, this is probably not advisable.

Since the spec file will normally be much smaller than the content to be 
installed, this should not be significant overhead in terms of space.

Note that a full update would include all files of the release, and in 
the spec file, the meta info of the new versions of these files.

If much content is changed, it might be advisable to produce a full update.

- Andr&#233;
</PRE>


<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="002957.html">[Mageia-discuss] Suggestions for the ISO
</A></li>
	<LI>Next message: <A HREF="002959.html">[Mageia-discuss] [OT] KDE 4.5.2 for Mandrive
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#2958">[ date ]</a>
              <a href="thread.html#2958">[ thread ]</a>
              <a href="subject.html#2958">[ subject ]</a>
              <a href="author.html#2958">[ author ]</a>
         </LI>
       </UL>

<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss
mailing list</a><br>
</body></html>