diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20110219/002668.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20110219/002668.html | 155 |
1 files changed, 155 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110219/002668.html b/zarb-ml/mageia-dev/20110219/002668.html new file mode 100644 index 000000000..9a2b4904d --- /dev/null +++ b/zarb-ml/mageia-dev/20110219/002668.html @@ -0,0 +1,155 @@ +<!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=%3C201102191541.51744.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="002665.html"> + <LINK REL="Next" HREF="002669.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=%3C201102191541.51744.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 15:41:51 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002665.html">[Mageia-dev] About panotools patent problem (and other problematic rpms) +</A></li> + <LI>Next message: <A HREF="002669.html">[Mageia-dev] About panotools patent problem (and other problematic rpms) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2668">[ date ]</a> + <a href="thread.html#2668">[ thread ]</a> + <a href="subject.html#2668">[ subject ]</a> + <a href="author.html#2668">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op zaterdag 19 februari 2011 14:59:46 schreef Michael Scherer: +><i> On Sat, 19 Feb 2011 09:20:50 +0100, Maarten Vanraes wrote: +</I>><i> > Op vrijdag 18 februari 2011 14:42:02 schreef Michael Scherer: +</I>><i> >> Le vendredi 18 février 2011 à 12:47 +0000, James Kerr a écrit : +</I>><i> >> > If there are two packages, one in core and another in tainted, +</I>><i> >> +</I>><i> >> then +</I>><i> >> +</I>><i> >> > doesn't urpmi need a way to recognise that the tainted package is +</I>><i> >> +</I>><i> >> newer +</I>><i> >> +</I>><i> >> > than (an update to) the corresponding core package? I believe that +</I>><i> >> +</I>><i> >> this +</I>><i> >> +</I>><i> >> > is achieved in Mandriva, because plf is greater than mdv. +</I>><i> >> +</I>><i> >> That's abusing release tag and it work by pure chance ( ie, had the +</I>><i> >> plf +</I>><i> >> decided to be called the guillomovitch liberation front, it would +</I>><i> >> not +</I>><i> >> have worked ). And this is quite inflexible, since people will +</I>><i> >> always +</I>><i> >> have plf packages, leading to users adding some rpm in skip.list +</I>><i> >> with a +</I>><i> >> regexp. +</I>><i> >> +</I>><i> >> This doesn't make much sense to treat tainted rpm as update to core, +</I>><i> >> this is not the same notion. But we cannot express this in urpmi for +</I>><i> >> the +</I>><i> >> moment, as this would requires some way to say "if you need to +</I>><i> >> install +</I>><i> >> something, prefer this source rather than this one". +</I>><i> >> +</I>><i> >> We can imagine a priority system, or we can simply say that if there +</I>><i> >> is +</I>><i> >> the same rpm on 2 media, we ask to the user ( except this would +</I>><i> >> requires +</I>><i> >> IMHO a better system than the current path based one to see what is +</I>><i> >> in a +</I>><i> >> rpm, but that's a rather long proposal to make ). +</I>><i> >> +</I>><i> >> But you are right this another set of issues to solve for dual life +</I>><i> >> packages. +</I>><i> > +</I>><i> > after sleeping on this, i've had this idea: +</I>><i> > +</I>><i> > why don't we rename packages in tainted? +</I>><i> > keeping them in the same name, perhaps has issues with search +</I>><i> > engines, (ie: +</I>><i> > which version do you get?) +</I>><i> +</I>><i> with search engine ? +</I>><i> I can see the issue for support, yes, but search engine, no +</I>><i> +</I>><i> > i proposed renaming packages in tainted,(but not the release tag). +</I>><i> > +</I>><i> > would it be a good compromise if we named packages: +</I>><i> > +</I>><i> > <orig_packagename>-tainted-<version>-<release> ? +</I>><i> > +</I>><i> > the benefit of this could be adding an Obsoletes and Provides on the +</I>><i> > original +</I>><i> > package with the identical version. +</I>><i> +</I>><i> This could work, but I am not sure that a Obsoletes is required. +</I>><i> +</I>><i> One problem with this idea is that it will ask to user lots of +</I>><i> questions, and that's +</I>><i> something we should rather try to avoid ( any people who installed some +</I>><i> java rpm will +</I>><i> understand the issue ). +</I>><i> +</I>><i> But it has the advantage of not requiring anything special on BS while +</I>><i> providing the choice. +</I> +if there is obsoletes, i don't think a question will be asked... + +><i> > for building, i may have this solution: +</I>><i> > +</I>><i> > %tainted(%_optional_feature1 %optional_feature2 %optional_feature3) +</I>><i> > +</I>><i> > this would allow the buildbot to look for %tainted and if it does, +</I>><i> > it could +</I>><i> > rebuild it for tainted and add the particulars itself. this would +</I>><i> > simplify the +</I>><i> > whole plf/tainted thing easily. and since all 4 rpms are being built +</I>><i> > at the +</I>><i> > same time, you have no srpm problem either. +</I>><i> +</I>><i> A simple %define would do the trick, so that doesn't bring much. +</I>><i> And we can keep a list of package that should be compiled twice, that's +</I>><i> not the biggest problem to solve. +</I> + +well, it's an idea, that allows us to have all the functionality we want, and +no manual intervention needed anymore. +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002665.html">[Mageia-dev] About panotools patent problem (and other problematic rpms) +</A></li> + <LI>Next message: <A HREF="002669.html">[Mageia-dev] About panotools patent problem (and other problematic rpms) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2668">[ date ]</a> + <a href="thread.html#2668">[ thread ]</a> + <a href="subject.html#2668">[ subject ]</a> + <a href="author.html#2668">[ 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> |