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
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
|
<!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=%3C4F0BB7CE.7060901%40laposte.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="011189.html">
<LINK REL="Next" HREF="011191.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=%3C4F0BB7CE.7060901%40laposte.net%3E"
TITLE="[Mageia-dev] [RFC] Moving various packages/codecs to tainted">andre999mga at laposte.net
</A><BR>
<I>Tue Jan 10 05:00:14 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="011189.html">[Mageia-dev] [RFC] Moving various packages/codecs to tainted
</A></li>
<LI>Next message: <A HREF="011191.html">[Mageia-dev] [RFC] Moving various packages/codecs to tainted
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#11196">[ date ]</a>
<a href="thread.html#11196">[ thread ]</a>
<a href="subject.html#11196">[ subject ]</a>
<a href="author.html#11196">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Frank Griffin a écrit :
><i> On 01/09/2012 06:38 PM, Anssi Hannula wrote:
</I>>><i> On 10.01.2012 01:30, David Walser wrote:
</I>>><i>
</I>>>><i> That's the absolute last thing I want to see happen. It's one of
</I>>>><i> the reasons Fedora and others that do that are not viable options
</I>>>><i> for a lot
</I>>>><i> of non-technical users, and it just makes it so you have to jump
</I>>>><i> through a lot of extra hoops just to have a reasonably working system
</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.
</I>><i>
</I>><i> I agree with both of you, but the problem is the difference between
</I>><i> non-free and tainted. Unfortunately, both are required for a
</I>><i> "reasonably working system". But in the case of nonfree, it's just a
</I>><i> matter of us internally getting past the "purity of the media" issue.
</I>><i> In the case of tainted, there are legal issues.
</I>
Patent claims are potential legal issues, since among other things, most
claims are invalidated when (or before) they reach the courts. So it
makes much more sense to wait for real legal patent threats. Agreed, it
does make sense to put packages in "tainted" when real threats arise.
Such cases will impact much bigger and richer targets before us, so we
will have plenty of time to react.
><i> I think that the ultimate solution is going to have to be integrated
</I>><i> support in the installer allowing the user to hook up either nonfree,
</I>><i> tainted, or both, just by answering a simple prompt. The mirror
</I>><i> database probably ought to (if it doesn't already) keep track of which
</I>><i> mirrors supply nonfree and tainted (or better still, check at install
</I>><i> time), and customize mirror selection based on the user's response.
</I>
Good idea.
Note that only "tainted" is optional on official mirrors. (Yet they all
seem to carry "tainted", including in the apparently "patent-threatened"
countries such as the U.S.)
><i> For non-network installs, I don't see a way around separate ISOs, at
</I>><i> least for tainted.
</I>
Another reason why we should limit what goes into tainted. Since many
users don't have a connexion reliable enough for network install.
Our goal should be that it "just works out of the box", for as many
users as possible.
Without unduly compromising our commitment to open source, of course.
As for separate ISO's, if we go that route, we should arrive at some
solution that minimises the work involved (including testing) to produce
them. Such as maybe producing a DVD with enough non-free firmware and
drivers to get almost everyone's hardware working properly, and then
excluding the few non-free packages to produce a totally free DVD for
the purists.
(The non-free kernel-firmware package is only about 20M, for example.)
--
André
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="011189.html">[Mageia-dev] [RFC] Moving various packages/codecs to tainted
</A></li>
<LI>Next message: <A HREF="011191.html">[Mageia-dev] [RFC] Moving various packages/codecs to tainted
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#11196">[ date ]</a>
<a href="thread.html#11196">[ thread ]</a>
<a href="subject.html#11196">[ subject ]</a>
<a href="author.html#11196">[ 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>
|
