blob: 4a00049fcc2a36fad37c592ba740fc9c9de03162 (
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
91
|
<!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=%3Ck6eerh%24d7r%241%40ger.gmane.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="019128.html">
<LINK REL="Next" HREF="019547.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] rehashing the faac issue</H1>
<B>PhilippeDidier</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20rehashing%20the%20faac%20issue&In-Reply-To=%3Ck6eerh%24d7r%241%40ger.gmane.org%3E"
TITLE="[Mageia-dev] rehashing the faac issue">philippedidier at laposte.net
</A><BR>
<I>Fri Oct 26 18:47:49 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="019128.html">[Mageia-dev] rehashing the faac issue
</A></li>
<LI>Next message: <A HREF="019547.html">[Mageia-dev] rehashing the faac issue
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#19543">[ date ]</a>
<a href="thread.html#19543">[ thread ]</a>
<a href="subject.html#19543">[ subject ]</a>
<a href="author.html#19543">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Guillaume Rousse a écrit :
><i> Hello list.
</I>><i>
</I>><i> The case of faac package has been discussed several times already:
</I>><i> <A HREF="https://bugs.mageia.org/show_bug.cgi?id=1730">https://bugs.mageia.org/show_bug.cgi?id=1730</A>
</I>><i> <A HREF="http://www.mail-archive.com/mageia-dev@mageia.org/msg08059.html">http://www.mail-archive.com/mageia-dev@mageia.org/msg08059.html</A>
</I>><i>
</I>><i> <A HREF="https://www.mageia.org/pipermail/mageia-dev/2012-June/016673.html">https://www.mageia.org/pipermail/mageia-dev/2012-June/016673.html</A>
</I>><i>
</I>><i> So far, the conclusion was than we had no perfect solution to handle the
</I>><i> case of a software being having both licensing and patents issue,
</I>><i> whereas usually software only suffer from one of these problems only,
</I>><i> and than creating a dedicated 4th repository was unreasonable. Hence the
</I>><i> removal of the package from the mirrors (but not from our svn...).
</I>><i>
</I>><i> Given the importance of this package for several multimedia-related
</I>><i> software (it is a mandatory dependency for cinerella, for instance), I
</I>><i> think it's time to revisit this decision, and rather look for a
</I>><i> pragmatic solution rather than a merely bureaucratic one. So far, I
</I>><i> didn't see anything in the line of "we don't want to distribute it",
</I>><i> rather "we don't know how to do it"...
</I>><i>
</I>><i> For me, the simplest solution is just to decide between non-free and
</I>><i> tainted repository where this piece of code fits better (or sucks less),
</I>><i> eventually document the exception somewhere on the wiki, and stop
</I>><i> getting blocked eternally by our own rules...
</I>
unfortunately ...
three weeks after the last post on this thread
a long silence
and there is nothing new in Mageia...
Thanks again to Blogdrake's Repo !
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="019128.html">[Mageia-dev] rehashing the faac issue
</A></li>
<LI>Next message: <A HREF="019547.html">[Mageia-dev] rehashing the faac issue
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#19543">[ date ]</a>
<a href="thread.html#19543">[ thread ]</a>
<a href="subject.html#19543">[ subject ]</a>
<a href="author.html#19543">[ 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>
|