diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-January/011228.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-January/011228.html | 236 |
1 files changed, 236 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-January/011228.html b/zarb-ml/mageia-dev/2012-January/011228.html new file mode 100644 index 000000000..d0e877e05 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-January/011228.html @@ -0,0 +1,236 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] [RFC] Moving various packages/codecs to tainted + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BRFC%5D%20Moving%20various%20packages/codecs%20to%20tainted&In-Reply-To=%3C4F0D729C.7020801%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="011202.html"> + <LINK REL="Next" HREF="011267.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] [RFC] Moving various packages/codecs to tainted</H1> + <B>andre999</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BRFC%5D%20Moving%20various%20packages/codecs%20to%20tainted&In-Reply-To=%3C4F0D729C.7020801%40laposte.net%3E" + TITLE="[Mageia-dev] [RFC] Moving various packages/codecs to tainted">andre999mga at laposte.net + </A><BR> + <I>Wed Jan 11 12:29:32 CET 2012</I> + <P><UL> + <LI>Previous message: <A HREF="011202.html">[Mageia-dev] [RFC] Moving various packages/codecs to tainted +</A></li> + <LI>Next message: <A HREF="011267.html">[Mageia-dev] [RFC] Moving various packages/codecs to tainted +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#11228">[ date ]</a> + <a href="thread.html#11228">[ thread ]</a> + <a href="subject.html#11228">[ subject ]</a> + <a href="author.html#11228">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Colin Guthrie a écrit : +><i> 'Twas brillig, and andre999 at 10/01/12 03:12 did gyre and gimble: +</I>><i> +</I>>><i> Juan Luis Baptiste a écrit : +</I>>><i> +</I>>>><i> On Mon, Jan 9, 2012 at 6:38 PM, Anssi Hannula<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">anssi at mageia.org</A>> wrote: +</I>>>><i> +</I>>>><i> +</I>>>>><i> I'm absolutely fine with either moving codecs to core or tainted, as +</I>>>>><i> long as we are at least somewhat consistent in what is in core and what +</I>>>>><i> is in tainted. However, I do not really like the reasoning "we do it +</I>>>>><i> like mandriva did no matter if it is sensible or not". +</I>>>>><i> +</I>>>>><i> I'd possibly understand "we do it like mandriva did because they didn't +</I>>>>><i> apparently have problems with these pkgs", but it IMHO wouldn't really +</I>>>>><i> fly as we could just s/mandriva/ubuntu/ in that statement (and Ubuntu is +</I>>>>><i> much more prominent than mdv IMO) and then everything would be in +</I>>>>><i> core... +</I>>>>><i> +</I>>>>><i> +</I>>>>><i> +</I>>>><i> IMHO, for sake's of simplicity and user friendliness, we should leave +</I>>>><i> everything in core until there's a real threat from someone about +</I>>>><i> patents. Surely if it appears some day, we wouldn't be the first ones +</I>>>><i> to be approached which would leave us plenty of time to correct this +</I>>>><i> issue and move affected packages to tainted. +</I>>>><i> +</I>>>><i> +</I>>><i> I strongly agree with this approach. +</I>>><i> +</I>><i> I don't. Especially not with this message now in a public forum +</I>><i> admitting that we'd just be sticking our heads in the sand with regards +</I>><i> to this issue. +</I>><i> +</I>><i> If any legal action was taken, any efforts to plan for and deal with the +</I>><i> issues involved will be seen as a sign of good faith. This is very much +</I>><i> the opposite and thus would lead to stronger legal action should it ever +</I>><i> come to that. +</I>><i> +</I>><i> I really do not get the problem with splitting things out into the +</I>><i> appropriate repos. +</I>><i> +</I>><i> The only real question is about whether to enable those repos by default +</I>><i> and include the RPMs. +</I>><i> +</I> +We're talking about codecs, essentially the decoders which are used to +read encoded files. +If the patent claims are valid/enforceable (and most aren't), it is up +to the patent holder to decide if it is in their interest to enforce the +patent claims. +Since they will normally attempt to collect royalties from those using +the encoders to generate encoded content, it is in their interest avoid +enforcing claims against users of decoders, as the more such decoders +are used, the more the demand for the corresponding encoders, and thus +the more royalties they will collect. So it seems to me entirely +logical to await notification that they indeed intend to collect +royalties for these codec decoders. +However I do agree that we should put encoders that seem to be covered +by valid patents in some countries in "tainted". + +This might seem to be not worth the effort, particularly since, to the +best of my knowledge, even in software patent impacted countries such as +the U.S., no Linux mirror has chosen to not carry all the supposedly +patent-affected packages produced by the distro. +However by including codec decoders on our isos, we will give users a +much more friendly experience, particularly those that can not use +online repos during installation. +We have to decide whether we would consider a package affected by patents. +I'm just trying to suggest that we hold off putting codec decoders in +"tainted" until we know that the patent holder intends to enforce the +patent (against us or other similar users). + +Of course we could always be dogmatic about it. It would be interesting +producing a release the next time there is a claim against the Linux kernel. + +><i> The split is a purely technical decision that should (in theory at +</I>><i> least) have zero impact on a default install unless we specifically +</I>><i> decide to allow it to. +</I>><i> +</I> +One could say that there is a considerable political side of the issue. +Is the claim potentially valid ? (We probably already consider that, to +some degree.) +Does the patent holder intend to enforce it, in our context. (We should +consider that.) + +As far as the impact goes, if we don't separate likely enforced from +other patent claims, we won't be able to provide codecs on our DVD's, +which will impact those who can not reliably do a network install. +I'd rather that Mageia be known as a user-friendly distro. + +><i> Col +</I>><i> +</I>><i> +</I> +My 2 cents :) + +-- +André + +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="011202.html">[Mageia-dev] [RFC] Moving various packages/codecs to tainted +</A></li> + <LI>Next message: <A HREF="011267.html">[Mageia-dev] [RFC] Moving various packages/codecs to tainted +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#11228">[ date ]</a> + <a href="thread.html#11228">[ thread ]</a> + <a href="subject.html#11228">[ subject ]</a> + <a href="author.html#11228">[ 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> |