summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-December/020842.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2012-December/020842.html')
-rw-r--r--zarb-ml/mageia-dev/2012-December/020842.html88
1 files changed, 88 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-December/020842.html b/zarb-ml/mageia-dev/2012-December/020842.html
new file mode 100644
index 000000000..1c36cec9d
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-December/020842.html
@@ -0,0 +1,88 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] The &#171;task-obsolete&#187; debate [Was: 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%0A%20%3D%3Futf-8%3Fq%3FThe_%3DC2%3DABtask-obsolete%3DC2%3DBB_debate_%3D5BWa%3F%3D%0A%20%3D%3Futf-8%3Fq%3Fs%3D3A_Package_drop_request%3D3A_ruby-ParseTree%3D5D%3F%3D&In-Reply-To=%3C20121218195807.GC4767%40shikamaru.fr%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="020733.html">
+ <LINK REL="Next" HREF="020642.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] The &#171;task-obsolete&#187; debate [Was: Package drop request: ruby-ParseTree]</H1>
+ <B>Remy CLOUARD</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%0A%20%3D%3Futf-8%3Fq%3FThe_%3DC2%3DABtask-obsolete%3DC2%3DBB_debate_%3D5BWa%3F%3D%0A%20%3D%3Futf-8%3Fq%3Fs%3D3A_Package_drop_request%3D3A_ruby-ParseTree%3D5D%3F%3D&In-Reply-To=%3C20121218195807.GC4767%40shikamaru.fr%3E"
+ TITLE="[Mageia-dev] The &#171;task-obsolete&#187; debate [Was: Package drop request: ruby-ParseTree]">shikamaru at mageia.org
+ </A><BR>
+ <I>Tue Dec 18 20:58:07 CET 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="020733.html">[Mageia-dev] The &#171;task-obsolete&#187; debate [Was: Package drop request: ruby-ParseTree]
+</A></li>
+ <LI>Next message: <A HREF="020642.html">[Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-37.mga3
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#20842">[ date ]</a>
+ <a href="thread.html#20842">[ thread ]</a>
+ <a href="subject.html#20842">[ subject ]</a>
+ <a href="author.html#20842">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On Tue, Dec 11, 2012 at 03:29:11AM +0100, Johnny A. Solbu wrote:
+&gt;<i> Another thing is that some pakcages listed in task-obsolete clearly doesn't belong there.
+</I>&gt;<i> I took a quick glance on the spec file for task-obsolete. and I notice that some of the packages listed should be listed in the packages that replace them.
+</I>&gt;<i> One example is &#171;policykit&#187; where the comment says is replaced by &#171;polkit&#187;. I've read in other mails on this list that in situations where a package is replaced by a package with another name, the new package should obsolete the old one.
+</I>&gt;<i>
+</I>I&#8217;m not so sure about that. The problem with obsoletes is that once you
+put it in the spec you can&#8217;t remove it until the last supported release
+that included the old package is eol&#8217;d (and assuming one doesn&#8217;t upgrade
+from a very old release straight to the last one).
+
+The consequence of this is that over time spec files tend to carry a lot
+of history which kind of gets in the way. Having a task-obsolete is a
+nice way to tidy specfiles and have all that garbage in only one can.
+
+It can also help automating cleanup, because there&#8217;s only one spec file
+to update once a distribution gets eol&#8217;d. With obsoletes in each spec
+file we tend to forget these obsoletes are obsolete themselves and carry
+useless instructions.
+
+Of course it means more work first because you have 2 packages to modify
+and submit, but in the long run I think it can help keeping the specs
+clear, and I hope the intent of this package was this.
+
+I may be wrong, but if you agree with that, a nice addition would be to
+add a convention, no wait, a policy to tell how to add a package to
+task-obsolete like adding a comment before with a timestamp or a
+distribution release number so that it can effectively be cleaned.
+
+Regards,
+--
+R&#233;my CLOUARD
+() ascii ribbon campaign - against html e-mail
+/\ www.asciiribbon.org - against proprietary attachments
+</PRE>
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="020733.html">[Mageia-dev] The &#171;task-obsolete&#187; debate [Was: Package drop request: ruby-ParseTree]
+</A></li>
+ <LI>Next message: <A HREF="020642.html">[Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-37.mga3
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#20842">[ date ]</a>
+ <a href="thread.html#20842">[ thread ]</a>
+ <a href="subject.html#20842">[ subject ]</a>
+ <a href="author.html#20842">[ 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>