blob: 75fba4136a8301bbed3e9b99d95a569c53490a01 (
plain)
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
101
102
103
104
105
106
107
108
109
110
111
112
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] [ANN] [RFC] support for deltarpms in urpmi
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BANN%5D%20%5BRFC%5D%20support%20for%20deltarpms%20in%20urpmi&In-Reply-To=%3CCAONrEtYczFVUq-ZgkoqFyOuH68Luhgw8MOh2D%3DeOWm3VVDJpQg%40mail.gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="020349.html">
<LINK REL="Next" HREF="020354.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] [ANN] [RFC] support for deltarpms in urpmi</H1>
<B>Thierry Vignaud</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BANN%5D%20%5BRFC%5D%20support%20for%20deltarpms%20in%20urpmi&In-Reply-To=%3CCAONrEtYczFVUq-ZgkoqFyOuH68Luhgw8MOh2D%3DeOWm3VVDJpQg%40mail.gmail.com%3E"
TITLE="[Mageia-dev] [ANN] [RFC] support for deltarpms in urpmi">thierry.vignaud at gmail.com
</A><BR>
<I>Tue Nov 27 17:10:06 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="020349.html">[Mageia-dev] Tonight's meeting
</A></li>
<LI>Next message: <A HREF="020354.html">[Mageia-dev] [ANN] [RFC] support for deltarpms in urpmi
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#20348">[ date ]</a>
<a href="thread.html#20348">[ thread ]</a>
<a href="subject.html#20348">[ subject ]</a>
<a href="author.html#20348">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Hi
urpmi now have basic support for delta rpms, aka it can install them
(never worked before).
We could think about providing updates as delta rpms for mga3.
Example for libreoffice:
both
core/release/libreoffice-writer-3.5.3.2-1.mga2.x86_64.rpm and
libreoffice-writer-3.5.5.3-0.3.mga2.x86_64.rpm
are 4,2M big but:
makedeltarpm core/release/libreoffice-writer-3.5.3.2-1.mga2.x86_64.rpm
core/updates/libreoffice-writer-3.5.5.3-0.3.mga2.x86_64.rpm
/tmp/libreoffice-writer-3.5.5.3-0.3.mga2.x86_64.drpm2
results in a 405k delta rpm.
Aka a 10 fold reduction in download needs.
We should think about what's needed:
- new deltarpm update media to hold deltarpms ?
- recording source version in synthesis
- keeping:
o all deltarpm (not as big as full classic rpms)
o or only keeping both:
* core/release > latest core/updates
* previous core/updates > latest core/updates
- option do disable deltarpm support in /etc/urpmi.cfg?
- having a fallback in urpmi if applydeltarpm fails
- having urpmi select the right package
o either deltarpm if there's one for installed_version -> update_version path
o or regular update package else
WDYT?
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="020349.html">[Mageia-dev] Tonight's meeting
</A></li>
<LI>Next message: <A HREF="020354.html">[Mageia-dev] [ANN] [RFC] support for deltarpms in urpmi
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#20348">[ date ]</a>
<a href="thread.html#20348">[ thread ]</a>
<a href="subject.html#20348">[ subject ]</a>
<a href="author.html#20348">[ 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>
|
