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/2012-December/020716.html | 80 ++++++++++++++++++++++++++++ 1 file changed, 80 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-December/020716.html (limited to 'zarb-ml/mageia-dev/2012-December/020716.html') diff --git a/zarb-ml/mageia-dev/2012-December/020716.html b/zarb-ml/mageia-dev/2012-December/020716.html new file mode 100644 index 000000000..12c76d23e --- /dev/null +++ b/zarb-ml/mageia-dev/2012-December/020716.html @@ -0,0 +1,80 @@ + + + + [Mageia-dev] Package drop request: ruby-ParseTree + + + + + + + + + +

[Mageia-dev] Package drop request: ruby-ParseTree

+ nicolas vigier + boklm at mars-attacks.org +
+ Mon Dec 10 16:07:21 CET 2012 +

+
+ +
On Mon, 10 Dec 2012, Colin Guthrie wrote:
+
+> 
+> > Maybe instead of obsoleting packages, task-obsolete could conflict with
+> > those packages :
+> 
+> Could it obsolete *and* conflict packages and get the best of both
+> worlds? If that was the case it should work both from a UI level and
+> also from a structural (i.e. repository) level.
+> 
+> If that works, then we just define a simple macro at the top of the spec
+> and use it throughout:
+> 
+> %kill foo
+> %kill wibble
+> 
+> etc. which automatically adds both the conflicts and the obsoletes tags.
+
+I don't know what urpmi/rpmdrake is doing when there is both a conflict
+and an obsolete. If it is doing the same as what we have now with
+only obsolete, but with a warning, it looks like a good idea.
+
+
+ + + + + +
+

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