blob: 4b5db1b08a1c674875e670eee1da60b18dc75bdf (
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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-sysadm] changing binrepos
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20changing%20binrepos&In-Reply-To=%3C4E2036B4.2080109%40colin.guthr.ie%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="003733.html">
<LINK REL="Next" HREF="003735.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-sysadm] changing binrepos</H1>
<B>Colin Guthrie</B>
<A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20changing%20binrepos&In-Reply-To=%3C4E2036B4.2080109%40colin.guthr.ie%3E"
TITLE="[Mageia-sysadm] changing binrepos">mageia at colin.guthr.ie
</A><BR>
<I>Fri Jul 15 14:46:44 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="003733.html">[Mageia-sysadm] changing binrepos
</A></li>
<LI>Next message: <A HREF="003735.html">[Mageia-sysadm] changing binrepos
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#3734">[ date ]</a>
<a href="thread.html#3734">[ thread ]</a>
<a href="subject.html#3734">[ subject ]</a>
<a href="author.html#3734">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>'Twas brillig, and Sander Lepik at 15/07/11 07:14 did gyre and gimble:
><i> 15.07.2011 00:32, Colin Guthrie kirjutas:
</I>>><i>
</I>>><i> Just to be sure, why not make the file name "sha1sum-size", that way
</I>>><i> you're massively decreasing the likelihood of an sha1sum clash.
</I>>><i>
</I>>><i> Col
</I>>><i>
</I>><i> Or %{name}-sha1sum - easy to search by package if needed.
</I>
Nah, because that way, things that share sources (such as different
kernel packages) would not be able to get disk-space (on server side)
saving benefits and also some packages (I presume you intended %{name}
to be the one from the spec?) will have multiple binary sources.
But now I think about it, if 2+ packages do share the same binary, how
do we know it's OK to actually delete the binary from the binrepos? We'd
have to check every single packages sha1.lst file to see if it used
it... that doesn't sound ideal....
Col
--
Colin Guthrie
mageia(at)colin.guthr.ie
<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A>
Day Job:
Tribalogic Limited [<A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A>]
Open Source:
Mageia Contributor [<A HREF="http://www.mageia.org/">http://www.mageia.org/</A>]
PulseAudio Hacker [<A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A>]
Trac Hacker [<A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A>]
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="003733.html">[Mageia-sysadm] changing binrepos
</A></li>
<LI>Next message: <A HREF="003735.html">[Mageia-sysadm] changing binrepos
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#3734">[ date ]</a>
<a href="thread.html#3734">[ thread ]</a>
<a href="subject.html#3734">[ subject ]</a>
<a href="author.html#3734">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm
mailing list</a><br>
</body></html>
|