summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20110222/002743.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/20110222/002743.html')
-rw-r--r--zarb-ml/mageia-dev/20110222/002743.html134
1 files changed, 134 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110222/002743.html b/zarb-ml/mageia-dev/20110222/002743.html
new file mode 100644
index 000000000..a030effea
--- /dev/null
+++ b/zarb-ml/mageia-dev/20110222/002743.html
@@ -0,0 +1,134 @@
+<!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%0A%20%3D%3Futf-8%3Fq%3FAbout_panotools_patent_problem_%3D28and_othe%3F%3D%0A%20%3D%3Futf-8%3Fq%3Fr%3D09problematic_rpms%3D29%3F%3D&In-Reply-To=%3C201102222318.54113.bgmilne%40staff.telkomsa.net%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="002740.html">
+ <LINK REL="Next" HREF="002744.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] About panotools patent problem (and other problematic rpms)</H1>
+ <B>Buchan Milne</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%0A%20%3D%3Futf-8%3Fq%3FAbout_panotools_patent_problem_%3D28and_othe%3F%3D%0A%20%3D%3Futf-8%3Fq%3Fr%3D09problematic_rpms%3D29%3F%3D&In-Reply-To=%3C201102222318.54113.bgmilne%40staff.telkomsa.net%3E"
+ TITLE="[Mageia-dev] About panotools patent problem (and other problematic rpms)">bgmilne at staff.telkomsa.net
+ </A><BR>
+ <I>Tue Feb 22 22:18:53 CET 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="002740.html">[Mageia-dev] About panotools patent problem (and other problematic rpms)
+</A></li>
+ <LI>Next message: <A HREF="002744.html">[Mageia-dev] About panotools patent problem (and other problematic rpms)
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#2743">[ date ]</a>
+ <a href="thread.html#2743">[ thread ]</a>
+ <a href="subject.html#2743">[ subject ]</a>
+ <a href="author.html#2743">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On Tuesday, 22 February 2011 20:09:17 andre999 wrote:
+&gt;<i> Maarten Vanraes a &#233;crit :
+</I>&gt;<i> &gt; Op vrijdag 18 februari 2011 14:42:02 schreef Michael Scherer:
+</I>&gt;<i> &gt;&gt; Le vendredi 18 f&#233;vrier 2011 &#224; 12:47 +0000, James Kerr a &#233;crit :
+</I>&gt;<i> &gt;&gt;&gt; If there are two packages, one in core and another in tainted, then
+</I>&gt;<i> &gt;&gt;&gt; doesn't urpmi need a way to recognise that the tainted package is newer
+</I>&gt;<i> &gt;&gt;&gt; than (an update to) the corresponding core package? I believe that this
+</I>&gt;<i> &gt;&gt;&gt; is achieved in Mandriva, because plf is greater than mdv.
+</I>&gt;<i> &gt;&gt;
+</I>&gt;<i> &gt;&gt; That's abusing release tag and it work by pure chance ( ie, had the plf
+</I>&gt;<i> &gt;&gt; decided to be called the guillomovitch liberation front, it would not
+</I>&gt;<i> &gt;&gt; have worked ). And this is quite inflexible, since people will always
+</I>&gt;<i> &gt;&gt; have plf packages, leading to users adding some rpm in skip.list with a
+</I>&gt;<i> &gt;&gt; regexp.
+</I>&gt;<i> &gt;&gt;
+</I>&gt;<i> &gt;&gt; This doesn't make much sense to treat tainted rpm as update to core,
+</I>&gt;<i> &gt;&gt; this is not the same notion. But we cannot express this in urpmi for the
+</I>&gt;<i> &gt;&gt; moment, as this would requires some way to say &quot;if you need to install
+</I>&gt;<i> &gt;&gt; something, prefer this source rather than this one&quot;.
+</I>&gt;<i> &gt;&gt;
+</I>&gt;<i> &gt;&gt; We can imagine a priority system, or we can simply say that if there is
+</I>&gt;<i> &gt;&gt; the same rpm on 2 media, we ask to the user ( except this would requires
+</I>&gt;<i> &gt;&gt; IMHO a better system than the current path based one to see what is in a
+</I>&gt;<i> &gt;&gt; rpm, but that's a rather long proposal to make ).
+</I>&gt;<i> &gt;&gt;
+</I>&gt;<i> &gt;&gt; But you are right this another set of issues to solve for dual life
+</I>&gt;<i> &gt;&gt; packages.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; after sleeping on this, i've had this idea:
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; why don't we rename packages in tainted?
+</I>&gt;<i> &gt; keeping them in the same name, perhaps has issues with search engines,
+</I>&gt;<i> &gt; (ie: which version do you get?)
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; i proposed renaming packages in tainted,(but not the release tag).
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; would it be a good compromise if we named packages:
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; &lt;orig_packagename&gt;-tainted-&lt;version&gt;-&lt;release&gt; ?
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; the benefit of this could be adding an Obsoletes and Provides on the
+</I>&gt;<i> &gt; original package with the identical version.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; for building, i may have this solution:
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; %tainted(%_optional_feature1 %optional_feature2 %optional_feature3)
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; this would allow the buildbot to look for %tainted and if it does, it
+</I>&gt;<i> &gt; could rebuild it for tainted and add the particulars itself. this would
+</I>&gt;<i> &gt; simplify the whole plf/tainted thing easily. and since all 4 rpms are
+</I>&gt;<i> &gt; being built at the same time, you have no srpm problem either.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; WDYT?
+</I>&gt;<i>
+</I>&gt;<i> &lt;aside&gt;
+</I>&gt;<i> First of all, &quot;tainted&quot; in English implies that the software doesn't
+</I>&gt;<i> work.
+</I>
+I have never seen that interpretation. Tainted is a synonym for contaminated.
+Contaminated doesn't mean that it doesn't work, it means that you should
+exercise caution in using it (e.g. you may not want to drink it, but you can
+use it to wash your car).
+
+<A HREF="http://www.encyclopedia.com/doc/1O999-taint.html">http://www.encyclopedia.com/doc/1O999-taint.html</A>
+
+&gt;<i> (Unless it refers to food, in which case it means &quot;poisonous&quot;.)
+</I>&gt;<i> So we should choose a more appropriate name, such as &quot;constrained&quot;, or
+</I>&gt;<i> use the Ubuntu approach and use a name which doesn't literally describe
+</I>&gt;<i> the contents. (&quot;Multiverse&quot;, in their case.)
+</I>&gt;<i> Anything but something that implies that there is something inherently
+</I>&gt;<i> wrong with the package in question.
+</I>
+There is something wrong with the package, it is contaminated by software
+patents.
+
+Regards,
+Buchan
+</PRE>
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="002740.html">[Mageia-dev] About panotools patent problem (and other problematic rpms)
+</A></li>
+ <LI>Next message: <A HREF="002744.html">[Mageia-dev] About panotools patent problem (and other problematic rpms)
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#2743">[ date ]</a>
+ <a href="thread.html#2743">[ thread ]</a>
+ <a href="subject.html#2743">[ subject ]</a>
+ <a href="author.html#2743">[ 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>