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-sysadm/2011-July/003736.html | 97 +++++++++++++++++++++++++++++ 1 file changed, 97 insertions(+) create mode 100644 zarb-ml/mageia-sysadm/2011-July/003736.html (limited to 'zarb-ml/mageia-sysadm/2011-July/003736.html') diff --git a/zarb-ml/mageia-sysadm/2011-July/003736.html b/zarb-ml/mageia-sysadm/2011-July/003736.html new file mode 100644 index 000000000..8d0dc0a6c --- /dev/null +++ b/zarb-ml/mageia-sysadm/2011-July/003736.html @@ -0,0 +1,97 @@ + + + + [Mageia-sysadm] changing binrepos + + + + + + + + + +

[Mageia-sysadm] changing binrepos

+ Pascal Terjan + pterjan at gmail.com +
+ Fri Jul 15 15:20:50 CEST 2011 +

+
+ +
On Fri, Jul 15, 2011 at 13:46, Colin Guthrie <mageia at colin.guthr.ie> wrote:
+> 'Twas brillig, and Sander Lepik at 15/07/11 07:14 did gyre and gimble:
+>> 15.07.2011 00:32, Colin Guthrie kirjutas:
+>>>
+>>> Just to be sure, why not make the file name "sha1sum-size", that way
+>>> you're massively decreasing the likelihood of an sha1sum clash.
+>>>
+>>> Col
+>>>
+>> Or %{name}-sha1sum - easy to search by package if needed.
+>
+> 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....
+
+I think <original filename>-<sha1> would be good to avoid both
+filename collision and sha1 collision while still sharing files
+between packages
+Regarding reference counting, I don't know the best way to do it :)
+
+In the original mail Nicolas said:
+> - when a file is no longer used, it is only removed from sha1.lst, not
+>  removed from the server
+> - If we want to save space, we can have a script to generate the list of
+> all used files from all packages, and remove files not in this list
+
+ + + + + + + + + + + +
+

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