blob: d0da11ec13a70ad6c1f588afdeb6ec8dfccfd040 (
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
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
|
<!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=%3C506BFCBB.8020204%40colin.guthr.ie%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="019155.html">
<LINK REL="Next" HREF="019158.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] rehashing the faac issue</H1>
<B>Colin Guthrie</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20rehashing%20the%20faac%20issue&In-Reply-To=%3C506BFCBB.8020204%40colin.guthr.ie%3E"
TITLE="[Mageia-dev] rehashing the faac issue">mageia at colin.guthr.ie
</A><BR>
<I>Wed Oct 3 10:52:11 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="019155.html">[Mageia-dev] rehashing the faac issue
</A></li>
<LI>Next message: <A HREF="019158.html">[Mageia-dev] rehashing the faac issue
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#19157">[ date ]</a>
<a href="thread.html#19157">[ thread ]</a>
<a href="subject.html#19157">[ subject ]</a>
<a href="author.html#19157">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>'Twas brillig, and Guillaume Rousse at 03/10/12 08:40 did gyre and gimble:
><i> Le 02/10/2012 23:58, PhilippeDidier a écrit :
</I>>><i> If the problem is really not soluble inside Mageia we can ask for a
</I>>><i> third party repo (guys from Blogdrake already provide FAAC, handbrake
</I>>><i> and cinerella... may we ask them to rebuild upon FAAC some Mageia's rpms
</I>>><i> ? the spec files are ready for this!)
</I>><i> It is perfectly soluble, and we don't need anyone else. If you reread
</I>><i> the thread, there is a consensus to use the tainted repository for
</I>><i> hosting it, provided some minor changes to its content definition first.
</I>
Just as a possible solution here (which might actually make life easier
generally and perhaps even see the deprecation of the non-free
repository completely....
Could we add a "license blacklist" (or whitelist) feature to URMI?
We could maintain a list of non-free (or free) licenses and users who
prefer foss only, could easily configure their systems (it could be the
default) to reject any RPM where the license does not match the rules.
This way we only have core and tainted. The only issue is patents or
not. The rest is just sorted out by filtering by the tools involved.
Just a suggestion.
Col
--
Colin Guthrie
colin(at)mageia.org
<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A>
Day Job:
Tribalogic Limited <A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A>
Open Source:
Mageia Contributor <A HREF="http://www.mageia.org/">http://www.mageia.org/</A>
PulseAudio Hacker <A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A>
Trac Hacker <A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="019155.html">[Mageia-dev] rehashing the faac issue
</A></li>
<LI>Next message: <A HREF="019158.html">[Mageia-dev] rehashing the faac issue
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#19157">[ date ]</a>
<a href="thread.html#19157">[ thread ]</a>
<a href="subject.html#19157">[ subject ]</a>
<a href="author.html#19157">[ 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>
|
