diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-December/020716.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-December/020716.html | 80 |
1 files changed, 80 insertions, 0 deletions
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 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Package drop request: ruby-ParseTree + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Package%20drop%20request%3A%20ruby-ParseTree&In-Reply-To=%3C20121210150721.GS21938%40mars-attacks.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="020713.html"> + <LINK REL="Next" HREF="020715.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Package drop request: ruby-ParseTree</H1> + <B>nicolas vigier</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Package%20drop%20request%3A%20ruby-ParseTree&In-Reply-To=%3C20121210150721.GS21938%40mars-attacks.org%3E" + TITLE="[Mageia-dev] Package drop request: ruby-ParseTree">boklm at mars-attacks.org + </A><BR> + <I>Mon Dec 10 16:07:21 CET 2012</I> + <P><UL> + <LI>Previous message: <A HREF="020713.html">[Mageia-dev] Package drop request: ruby-ParseTree +</A></li> + <LI>Next message: <A HREF="020715.html">[Mageia-dev] Package drop request: ruby-ParseTree +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#20716">[ date ]</a> + <a href="thread.html#20716">[ thread ]</a> + <a href="subject.html#20716">[ subject ]</a> + <a href="author.html#20716">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Mon, 10 Dec 2012, Colin Guthrie wrote: + +><i> +</I>><i> > Maybe instead of obsoleting packages, task-obsolete could conflict with +</I>><i> > those packages : +</I>><i> +</I>><i> Could it obsolete *and* conflict packages and get the best of both +</I>><i> worlds? If that was the case it should work both from a UI level and +</I>><i> also from a structural (i.e. repository) level. +</I>><i> +</I>><i> If that works, then we just define a simple macro at the top of the spec +</I>><i> and use it throughout: +</I>><i> +</I>><i> %kill foo +</I>><i> %kill wibble +</I>><i> +</I>><i> etc. which automatically adds both the conflicts and the obsoletes tags. +</I> +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. + +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="020713.html">[Mageia-dev] Package drop request: ruby-ParseTree +</A></li> + <LI>Next message: <A HREF="020715.html">[Mageia-dev] Package drop request: ruby-ParseTree +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#20716">[ date ]</a> + <a href="thread.html#20716">[ thread ]</a> + <a href="subject.html#20716">[ subject ]</a> + <a href="author.html#20716">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |