diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20110218/002656.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20110218/002656.html | 121 |
1 files changed, 121 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110218/002656.html b/zarb-ml/mageia-dev/20110218/002656.html new file mode 100644 index 000000000..726bb43f6 --- /dev/null +++ b/zarb-ml/mageia-dev/20110218/002656.html @@ -0,0 +1,121 @@ +<!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%20problematic%20rpms%29&In-Reply-To=%3C1298030872.23751.26.camel%40akroma.ephaone.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002654.html"> + <LINK REL="Next" HREF="002658.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] About panotools patent problem (and other problematic rpms)</H1> + <B>Michael Scherer</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20About%20panotools%20patent%20problem%20%28and%20other%0A%20problematic%20rpms%29&In-Reply-To=%3C1298030872.23751.26.camel%40akroma.ephaone.org%3E" + TITLE="[Mageia-dev] About panotools patent problem (and other problematic rpms)">misc at zarb.org + </A><BR> + <I>Fri Feb 18 13:07:52 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002654.html">[Mageia-dev] About panotools patent problem (and other problematic rpms) +</A></li> + <LI>Next message: <A HREF="002658.html">[Mageia-dev] About panotools patent problem (and other problematic rpms) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2656">[ date ]</a> + <a href="thread.html#2656">[ thread ]</a> + <a href="subject.html#2656">[ subject ]</a> + <a href="author.html#2656">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le vendredi 18 février 2011 à 12:43 +0100, Oliver Burger a écrit : +><i> Philippe DIDIER <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">philippedidier at laposte.net</A>> schrieb am 2011-02-18 +</I>><i> > And what I talked about (in the other thread with the same name) +</I>><i> > was about the easiness to build and use different rpms with the +</I>><i> > same spec having mdv versus plf suffixes... +</I>><i> > And about it seems that we need to have different naming for Mageia +</I>><i> > (whether it's a "normal" or tainted rpm) +</I>><i> I still don't see a reason for this. We devide those packages by the +</I>><i> repo they get in, why do another thing? +</I> +><i>From a build system point f view, this is easier to indeed treat that +</I>like non-free, because there is no modification to do. + +A better solution would indeed be to allow to have a tainted rpm in code +and tained, the core version being "cleaned" from litigious parts. + +let's take a exemple, let's imagine someone has a patent on a fictional +video codec let's call it MCVC ( MegaCompressionVideoCodec ), and a army +of cloned lawyers from Hell that enforce the patent in USA. + +Let's assume that Mplayer, as it support almost everything, support MCVC +in the current version. + +First solution : we move mplayer rpm to tainted, with support for MCVC. + +Second solution : we compile mplayer in core without support for MCVC + +Third solution : we compile mplayer 2 times, once in tainted with MCVC, +another one to core without. + + +The first solution force us to place everything that requires mplayer to +tainted, as core must be self contained. So that mean various frontends, +firefox plugin, etc. This could be problematic if we place some +libraries in tainted. ( like freetype ). + +The second solution may slightly annoy people with lots of holidays +movies encoded in MCVC. And would render tainted basically useless. + +The third solution is the one we use for PLF, but suffer from a few +technical issues : +- I am not sure the current system support it. In mdv, the 2 uploads +system are fully separated. Not here. + +- We need to make sure that the binaries and source rpms are kept in +sync. If I upload a new version of mplayer, it will erase the source rpm +and use the new one. So if I built the tainted one, the srpm that was +used for the core rpm is no longer here. + +- we need to make sure that the binaries rpms are in sync. If we upload +the core one, it would be nice to wait for the tainted one to be +uploaded too. Ie keep them in sync like we keep x86_64/i586 in sync. +But, only if the package is dual lived ( ie, there is rpms that will be +distributed only in tainted ). + +That's a rather non trivial problem to solve. + +And hopefully, we only have core and tainted ( ie, while non-free could +be added to the mix, there is no dual life issue with it ). + +-- +Michael Scherer + +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002654.html">[Mageia-dev] About panotools patent problem (and other problematic rpms) +</A></li> + <LI>Next message: <A HREF="002658.html">[Mageia-dev] About panotools patent problem (and other problematic rpms) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2656">[ date ]</a> + <a href="thread.html#2656">[ thread ]</a> + <a href="subject.html#2656">[ subject ]</a> + <a href="author.html#2656">[ 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> |