diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20110222/002740.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20110222/002740.html | 146 |
1 files changed, 146 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110222/002740.html b/zarb-ml/mageia-dev/20110222/002740.html new file mode 100644 index 000000000..b3f480572 --- /dev/null +++ b/zarb-ml/mageia-dev/20110222/002740.html @@ -0,0 +1,146 @@ +<!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=%3C201102222201.37593.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="002739.html"> + <LINK REL="Next" HREF="002743.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%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=%3C201102222201.37593.maarten.vanraes%40gmail.com%3E" + TITLE="[Mageia-dev] About panotools patent problem (and other problematic rpms)">maarten.vanraes at gmail.com + </A><BR> + <I>Tue Feb 22 22:01:37 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002739.html">[Mageia-dev] About panotools patent problem (and other problematic rpms) +</A></li> + <LI>Next message: <A HREF="002743.html">[Mageia-dev] About panotools patent problem (and other problematic rpms) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2740">[ date ]</a> + <a href="thread.html#2740">[ thread ]</a> + <a href="subject.html#2740">[ subject ]</a> + <a href="author.html#2740">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op dinsdag 22 februari 2011 19:09:17 schreef andre999: +><i> Maarten Vanraes a écrit : +</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, then +</I>><i> >>> doesn't urpmi need a way to recognise that the tainted package is newer +</I>><i> >>> than (an update to) the corresponding core package? I believe that this +</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 plf +</I>><i> >> decided to be called the guillomovitch liberation front, it would not +</I>><i> >> have worked ). And this is quite inflexible, since people will always +</I>><i> >> have plf packages, leading to users adding some rpm in skip.list 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 the +</I>><i> >> moment, as this would requires some way to say "if you need to 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 is +</I>><i> >> the same rpm on 2 media, we ask to the user ( except this would requires +</I>><i> >> IMHO a better system than the current path based one to see what is 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 engines, +</I>><i> > (ie: which version do you get?) +</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 package with the identical version. +</I>><i> > +</I>><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, it +</I>><i> > could rebuild it for tainted and add the particulars itself. this would +</I>><i> > simplify the whole plf/tainted thing easily. and since all 4 rpms are +</I>><i> > being built at the same time, you have no srpm problem either. +</I>><i> > +</I>><i> > WDYT? +</I>><i> +</I>><i> <aside> +</I>><i> First of all, "tainted" in English implies that the software doesn't +</I>><i> work. (Unless it refers to food, in which case it means "poisonous".) +</I>><i> So we should choose a more appropriate name, such as "constrained", or +</I>><i> use the Ubuntu approach and use a name which doesn't literally describe +</I>><i> the contents. ("Multiverse", in their case.) +</I>><i> Anything but something that implies that there is something inherently +</I>><i> wrong with the package in question. +</I>><i> That was one advantage of "plf", but of course that is already taken. +</I>><i> And it is certainly advantageous to include such packages directly on +</I>><i> Mageia mirrors. +</I>><i> </aside> +</I>><i> +</I>><i> A Cleaner approach -- albeit more work -- would be for the "constrained" +</I>><i> package to be an external module which adds the missing functionality. +</I>><i> For less modular packages, this would be replacing (only) the files +</I>><i> which provide the questioned functionality. +</I>><i> For a typical a music player-type application, this would be only a be a +</I>><i> few relatively small files. +</I>><i> +</I>><i> So a user that wants to add the "contrained" functionality would simply +</I>><i> add an extra package, which obviously would have a different name based +</I>><i> on the main package. +</I>><i> (It would be useful to suggest adding such packages during installation, +</I>><i> if the "contrained" repositories are selected.) +</I>><i> (That is, if such a related package is available in selected repos.) +</I>><i> +</I>><i> Think of the gstreamer packages -- the "ugly" perhaps corresponding to +</I>><i> the "constrained" packages being considered. +</I>><i> +</I>><i> my 2 cents :) +</I> +sure, but that doesn't always work, not all software is done like this +</PRE> + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002739.html">[Mageia-dev] About panotools patent problem (and other problematic rpms) +</A></li> + <LI>Next message: <A HREF="002743.html">[Mageia-dev] About panotools patent problem (and other problematic rpms) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2740">[ date ]</a> + <a href="thread.html#2740">[ thread ]</a> + <a href="subject.html#2740">[ subject ]</a> + <a href="author.html#2740">[ 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> |