blob: c475b1ed0a5aa5d2acf9b4d5ddcfc60381638229 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] 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%20rehashing%20the%20faac%20issue&In-Reply-To=%3Cm3hapc2a4f.fsf%40euphor.blino.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="019624.html">
<LINK REL="Next" HREF="019627.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] rehashing the faac issue</H1>
<B>Olivier Blin</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20rehashing%20the%20faac%20issue&In-Reply-To=%3Cm3hapc2a4f.fsf%40euphor.blino.org%3E"
TITLE="[Mageia-dev] rehashing the faac issue">mageia at blino.org
</A><BR>
<I>Mon Oct 29 23:20:48 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="019624.html">[Mageia-dev] rehashing the faac issue
</A></li>
<LI>Next message: <A HREF="019627.html">[Mageia-dev] rehashing the faac issue
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#19626">[ date ]</a>
<a href="thread.html#19626">[ thread ]</a>
<a href="subject.html#19626">[ subject ]</a>
<a href="author.html#19626">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Christiaan Welvaart <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">cjw at daneel.dyndns.org</A>> writes:
><i> The problem is the following:
</I>><i>
</I>><i> 1. faac cannot go into main (see 2 & 3)
</I>><i> 2. faac cannot go into tainted (it is not free software)
</I>><i> 3. faac cannot go into nonfree (patented in some countries)
</I>><i>
</I>><i> so we only have 2 options:
</I>><i> A. ban faac and use the AAC encoder(s) we already have in mageia
</I>><i> or another one that can go into tainted
</I>><i> B. add a special repository for faac
</I>><i>
</I>><i> I prefer option A and I patched a gstreamer based video encoding app
</I>><i> to use vo-aacenc instead of faac a while ago.
</I>
I would prefer B: adding a nonfree-tainted repo (+ its
updates/testing/backports/debug brothers).
See <A HREF="https://bugs.mageia.org/show_bug.cgi?id=2833">https://bugs.mageia.org/show_bug.cgi?id=2833</A> for a list of packages
needing faac.
Yes, that's overkill, it will clutter the urpmi media config UI, but
that's the only clean way we have.
I guess a simple way to unclutter the drakrpm-edit-media UI would be to
add a drop-down menu to select between "Release + Updates" (default and
most commonly used media), "Updates Testing", "Backports" (whenever it
gets in), and "Debug" (for debug packages of all aforementioned groups).
--
Olivier Blin - blino
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="019624.html">[Mageia-dev] rehashing the faac issue
</A></li>
<LI>Next message: <A HREF="019627.html">[Mageia-dev] rehashing the faac issue
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#19626">[ date ]</a>
<a href="thread.html#19626">[ thread ]</a>
<a href="subject.html#19626">[ subject ]</a>
<a href="author.html#19626">[ 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>
|
