summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20110219/002662.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/20110219/002662.html')
-rw-r--r--zarb-ml/mageia-dev/20110219/002662.html112
1 files changed, 112 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110219/002662.html b/zarb-ml/mageia-dev/20110219/002662.html
new file mode 100644
index 000000000..46bee60b4
--- /dev/null
+++ b/zarb-ml/mageia-dev/20110219/002662.html
@@ -0,0 +1,112 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] About panotools patent problem (and other problematic rpms)
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20About%20panotools%20patent%20problem%20%28and%20other%0A%09problematic%20rpms%29&In-Reply-To=%3C201102190920.50982.maarten.vanraes%40gmail.com%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="002671.html">
+ <LINK REL="Next" HREF="002665.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] About panotools patent problem (and other problematic rpms)</H1>
+ <B>Maarten Vanraes</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20About%20panotools%20patent%20problem%20%28and%20other%0A%09problematic%20rpms%29&In-Reply-To=%3C201102190920.50982.maarten.vanraes%40gmail.com%3E"
+ TITLE="[Mageia-dev] About panotools patent problem (and other problematic rpms)">maarten.vanraes at gmail.com
+ </A><BR>
+ <I>Sat Feb 19 09:20:50 CET 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="002671.html">[Mageia-dev] Is there any reason keeping ask.com as firefox's default search engine?
+</A></li>
+ <LI>Next message: <A HREF="002665.html">[Mageia-dev] About panotools patent problem (and other problematic rpms)
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#2662">[ date ]</a>
+ <a href="thread.html#2662">[ thread ]</a>
+ <a href="subject.html#2662">[ subject ]</a>
+ <a href="author.html#2662">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Op vrijdag 18 februari 2011 14:42:02 schreef Michael Scherer:
+&gt;<i> Le vendredi 18 f&#233;vrier 2011 &#224; 12:47 +0000, James Kerr a &#233;crit :
+</I>&gt;<i> &gt; If there are two packages, one in core and another in tainted, then
+</I>&gt;<i> &gt; doesn't urpmi need a way to recognise that the tainted package is newer
+</I>&gt;<i> &gt; than (an update to) the corresponding core package? I believe that this
+</I>&gt;<i> &gt; is achieved in Mandriva, because plf is greater than mdv.
+</I>&gt;<i>
+</I>&gt;<i> That's abusing release tag and it work by pure chance ( ie, had the plf
+</I>&gt;<i> decided to be called the guillomovitch liberation front, it would not
+</I>&gt;<i> have worked ). And this is quite inflexible, since people will always
+</I>&gt;<i> have plf packages, leading to users adding some rpm in skip.list with a
+</I>&gt;<i> regexp.
+</I>&gt;<i>
+</I>&gt;<i> This doesn't make much sense to treat tainted rpm as update to core,
+</I>&gt;<i> this is not the same notion. But we cannot express this in urpmi for the
+</I>&gt;<i> moment, as this would requires some way to say &quot;if you need to install
+</I>&gt;<i> something, prefer this source rather than this one&quot;.
+</I>&gt;<i>
+</I>&gt;<i> We can imagine a priority system, or we can simply say that if there is
+</I>&gt;<i> the same rpm on 2 media, we ask to the user ( except this would requires
+</I>&gt;<i> IMHO a better system than the current path based one to see what is in a
+</I>&gt;<i> rpm, but that's a rather long proposal to make ).
+</I>&gt;<i>
+</I>&gt;<i> But you are right this another set of issues to solve for dual life
+</I>&gt;<i> packages.
+</I>
+after sleeping on this, i've had this idea:
+
+why don't we rename packages in tainted?
+keeping them in the same name, perhaps has issues with search engines, (ie:
+which version do you get?)
+
+i proposed renaming packages in tainted,(but not the release tag).
+
+would it be a good compromise if we named packages:
+
+&lt;orig_packagename&gt;-tainted-&lt;version&gt;-&lt;release&gt; ?
+
+the benefit of this could be adding an Obsoletes and Provides on the original
+package with the identical version.
+
+for building, i may have this solution:
+
+%tainted(%_optional_feature1 %optional_feature2 %optional_feature3)
+
+this would allow the buildbot to look for %tainted and if it does, it could
+rebuild it for tainted and add the particulars itself. this would simplify the
+whole plf/tainted thing easily. and since all 4 rpms are being built at the
+same time, you have no srpm problem either.
+
+WDYT?
+</PRE>
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="002671.html">[Mageia-dev] Is there any reason keeping ask.com as firefox's default search engine?
+</A></li>
+ <LI>Next message: <A HREF="002665.html">[Mageia-dev] About panotools patent problem (and other problematic rpms)
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#2662">[ date ]</a>
+ <a href="thread.html#2662">[ thread ]</a>
+ <a href="subject.html#2662">[ subject ]</a>
+ <a href="author.html#2662">[ 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>