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

[Mageia-sysadm] changing binrepos

+ Sander Lepik + sander.lepik at eesti.ee +
+ Fri Jul 15 14:56:53 CEST 2011 +

+
+ +
15.07.2011 15:46, Colin Guthrie kirjutas:
+>
+> 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
+>
+Using database would help i think. Packages will be linked to files and 
+if all links are removed (ie all linked packages are EOL or using newer 
+version of binary source) then file becomes orphan and can be deleted.
+
+--
+Sander
+
+
+
+ + + + + + + + + + + +
+

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