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-dev/2011-December/010695.html | 86 ++++++++++++++++++++++++++++ 1 file changed, 86 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-December/010695.html (limited to 'zarb-ml/mageia-dev/2011-December/010695.html') diff --git a/zarb-ml/mageia-dev/2011-December/010695.html b/zarb-ml/mageia-dev/2011-December/010695.html new file mode 100644 index 000000000..d81b78aef --- /dev/null +++ b/zarb-ml/mageia-dev/2011-December/010695.html @@ -0,0 +1,86 @@ + + + + [Mageia-dev] RFP: commenting obsoletes for later removal + + + + + + + + + +

[Mageia-dev] RFP: commenting obsoletes for later removal

+ Per Øyvind Karlsen + peroyvind at mandriva.org +
+ Thu Dec 22 10:28:25 CET 2011 +

+
+ +
Den 14:13 17. desember 2011 skrev Maarten Vanraes <alien at rmail.be> følgende:
+> Hi all,
+>
+> Annsi, misc and myself were discussing obsoletes, and i think we should make a
+> policy for a structured comment, so that later (in some timeperiod that's as
+> of yet unspecified) we can remove older obsoletes in a structured way.
+>
+> I propose we put a comment in the spec file, with the version the package will
+> be first used, so likely that is cauldron, so example:
+>
+> # Obsoletes: mga2
+> (before the obsolete line)
+>
+>
+> if noone objects, we can put the policy on the wiki somewhere
+
+You could always comparing the metadata of different stable releases to try
+determine the age of these. I remember discussing this with pixel a
+few years ago,
+but it wasn't really an important issue and never given any priority,
+but implementing
+automated tests for this in ie. the youri(-related) tools would
+probably be a good idea. :)
+
+--
+Regards,
+Per Øyvind
+
+ + + + + + +
+

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