summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-November/019733.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2012-November/019733.html')
-rw-r--r--zarb-ml/mageia-dev/2012-November/019733.html138
1 files changed, 138 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-November/019733.html b/zarb-ml/mageia-dev/2012-November/019733.html
new file mode 100644
index 000000000..7c8f1f92e
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-November/019733.html
@@ -0,0 +1,138 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] cinelerra/audiokonverter/arista (war Re: rehashing the faac issue)
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20cinelerra/audiokonverter/arista%20%28war%20Re%3A%20rehashing%0A%20the%20faac%20issue%29&In-Reply-To=%3CCA%2Bh4nj5Q250V_jZLPPU%2B-OLXDp-OF8Y1GgjrmTaNAiq7OHBE9g%40mail.gmail.com%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="019731.html">
+ <LINK REL="Next" HREF="019734.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] cinelerra/audiokonverter/arista (war Re: rehashing the faac issue)</H1>
+ <B>Wolfgang Bornath</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20cinelerra/audiokonverter/arista%20%28war%20Re%3A%20rehashing%0A%20the%20faac%20issue%29&In-Reply-To=%3CCA%2Bh4nj5Q250V_jZLPPU%2B-OLXDp-OF8Y1GgjrmTaNAiq7OHBE9g%40mail.gmail.com%3E"
+ TITLE="[Mageia-dev] cinelerra/audiokonverter/arista (war Re: rehashing the faac issue)">molch.b at googlemail.com
+ </A><BR>
+ <I>Thu Nov 1 23:44:52 CET 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="019731.html">[Mageia-dev] cinelerra/audiokonverter/arista (war Re: rehashing the faac issue)
+</A></li>
+ <LI>Next message: <A HREF="019734.html">[Mageia-dev] cinelerra/audiokonverter/arista (war Re: rehashing the faac issue)
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#19733">[ date ]</a>
+ <a href="thread.html#19733">[ thread ]</a>
+ <a href="subject.html#19733">[ subject ]</a>
+ <a href="author.html#19733">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>2012/11/1 Christian Lohmaier &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">lohmaier+mageia at googlemail.com</A>&gt;:
+&gt;<i> Hi Wolfgang, *,
+</I>&gt;<i>
+</I>&gt;<i> On Thu, Nov 1, 2012 at 1:56 PM, Wolfgang Bornath &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">molch.b at googlemail.com</A>&gt; wrote:
+</I>&gt;&gt;<i> [...]
+</I>&gt;&gt;<i> After reading all arguments again I must confess that I changed my
+</I>&gt;&gt;<i> opinion: Being consequent and following our road we need a
+</I>&gt;&gt;<i> /tainted-free and a /tainted-nonfree branch.
+</I>&gt;<i>
+</I>&gt;<i> I still think this would be a very user-*un*friendly way to handle it.
+</I>&gt;<i>
+</I>&gt;<i> You cannot put packages that itself is &quot;free&quot;, but depends on
+</I>&gt;<i> &quot;tainted&amp;nonfree&quot; packages into the &quot;free&quot; repo, since the core repos
+</I>&gt;<i> need to be self-contained.
+</I>&gt;<i>
+</I>&gt;<i> The natural approach would then be to put that package into the same
+</I>&gt;<i> repo as the packages that fulfill the requirement.
+</I>&gt;<i>
+</I>&gt;<i> If now you have two tainted repositories, one &quot;free&quot; and one
+</I>&gt;<i> &quot;non-free&quot;, you would put the &quot;free with dependencies&quot; package into
+</I>&gt;<i> the tainted-free repo. But it itself isn't tainted, so actually
+</I>&gt;<i> wouldn't belong in there. But even when you have tainted-free enabled,
+</I>&gt;<i> and you try to install the package, you need to enable the
+</I>&gt;<i> tainted-nonfree one.
+</I>&gt;<i> Or you put it into tainted-nonfree to keep the repos more
+</I>&gt;<i> self-contained, but then the distinction is rendered useless, as
+</I>&gt;<i> packages end up there for completely different reasons.
+</I>&gt;<i>
+</I>&gt;<i> And if you have to enable both tainted variants anyway, there is no
+</I>&gt;<i> point in having them separate in the first place other than to please
+</I>&gt;<i> some bureaucratic nitpicking.
+</I>&gt;<i>
+</I>&gt;<i> So by creating a tainted-nonfree repo that only a handful of packages
+</I>&gt;<i> actually belong into anyway, you create a situation of non-satisfiable
+</I>&gt;<i> dependencies that make the distinction pointless from a user-POV.
+</I>&gt;<i>
+</I>&gt;<i> Much better would then be to create an &quot;ugly&quot; repo (in the spirit of
+</I>&gt;<i> gstreamer) that contains the &quot;doesn't fit into the other repos&quot; stuff.
+</I>&gt;<i>
+</I>&gt;<i> AFAIK only multimedia related stuff falls into tainted-nonfree. And it
+</I>&gt;<i> is either you want to use it or not. If you want to use it, the user
+</I>&gt;<i> doesn't care whether it is free or nonfree (by whatever definition,
+</I>&gt;<i> there isn't the one-and-only definition that everyone agrees with
+</I>&gt;<i> anyway). You only might care about whether it is tainted or not (and
+</I>&gt;<i> many don't give a damn about software patents even where they could
+</I>&gt;<i> apply in theory). It is not like you have a chance in most of these
+</I>&gt;<i> cases. Either you use a &quot;100% free but sucks&quot; implementation, or you
+</I>&gt;<i> use the &quot;tainted and possibly &quot;nonfree&quot;, but working just fine&quot; one.
+</I>
+Taking what you wrote into account there is no chance for a solution
+which also honors the division between free, non-free and tainted, at
+least non of the propositions in this thread would work. Because as
+you described the problem is not with each software but rather with
+its requirements (free software needing a non-free or tainted library
+to run or offer all its features).
+
+So what can we do? What do users want in such cases? First they do not
+want crippled packages. If they decide to have mplayer they want the
+whole thing, not a free variant which lacks features. They'd rather
+not want mplayer at all.
+
+Answering to this there may be a rather pragmatic but also drastic and
+even provocative solution: Stop offering software in core which need
+non-free and/or tainted libraries to give all its features. This
+software should not be offered in 2 or even 3 variants but only in one
+full version, residing in an &quot;ugly&quot; (or whatever you want to call it)
+repository.
+Yes, there may be people who would like to use mplayer without
+non-free or tainted libraries - but are there really? To my experience
+they either use the full blown package or another software.
+
+This solution may not hold against theoretical arguments but I think
+it's pretty much the practical way, for users as for packagers. And it
+will motivate people to search for free solutions where possible.
+
+--
+wobo
+</PRE>
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="019731.html">[Mageia-dev] cinelerra/audiokonverter/arista (war Re: rehashing the faac issue)
+</A></li>
+ <LI>Next message: <A HREF="019734.html">[Mageia-dev] cinelerra/audiokonverter/arista (war Re: rehashing the faac issue)
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#19733">[ date ]</a>
+ <a href="thread.html#19733">[ thread ]</a>
+ <a href="subject.html#19733">[ subject ]</a>
+ <a href="author.html#19733">[ 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>