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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] About panotools patent problem (and other problematic rpms)
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20About%20panotools%20patent%20problem%20%28and%20other%0A%20problematic%20rpms%29&In-Reply-To=%3C4D65F711.5060404%40laposte.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="002760.html">
<LINK REL="Next" HREF="002781.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] About panotools patent problem (and other problematic rpms)</H1>
<B>andre999</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20About%20panotools%20patent%20problem%20%28and%20other%0A%20problematic%20rpms%29&In-Reply-To=%3C4D65F711.5060404%40laposte.net%3E"
TITLE="[Mageia-dev] About panotools patent problem (and other problematic rpms)">andr55 at laposte.net
</A><BR>
<I>Thu Feb 24 07:13:37 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="002760.html">[Mageia-dev] time to switch from raw partitions to lvm?
</A></li>
<LI>Next message: <A HREF="002781.html">[Mageia-dev] About panotools patent problem (and other problematic rpms)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#2761">[ date ]</a>
<a href="thread.html#2761">[ thread ]</a>
<a href="subject.html#2761">[ subject ]</a>
<a href="author.html#2761">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Ahmad Samir a écrit :
><i>
</I>><i> On 22 February 2011 20:09, andre999<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">andr55 at laposte.net</A>> wrote:
</I>>><i>
</I>>><i> <aside>
</I>>><i> First of all, "tainted" in English implies that the software doesn't work.
</I>>><i> (Unless it refers to food, in which case it means "poisonous".)
</I>>><i> So we should choose a more appropriate name, such as "constrained", or use
</I>>><i> the Ubuntu approach and use a name which doesn't literally describe the
</I>>><i> contents. ("Multiverse", in their case.)
</I>>><i> Anything but something that implies that there is something inherently wrong
</I>>><i> with the package in question.
</I>>><i> That was one advantage of "plf", but of course that is already taken. And it
</I>>><i> is certainly advantageous to include such packages directly on Mageia
</I>>><i> mirrors.
</I>>><i> </aside>
</I>>><i>
</I>>><i> A Cleaner approach -- albeit more work -- would be for the "constrained"
</I>>><i> package to be an external module which adds the missing functionality. For
</I>>><i> less modular packages, this would be replacing (only) the files which
</I>>><i> provide the questioned functionality.
</I>>><i> For a typical a music player-type application, this would be only a be a few
</I>>><i> relatively small files.
</I>>><i>
</I>>><i> So a user that wants to add the "contrained" functionality would simply add
</I>>><i> an extra package, which obviously would have a different name based on the
</I>>><i> main package.
</I>>><i> (It would be useful to suggest adding such packages during installation, if
</I>>><i> the "contrained" repositories are selected.)
</I>>><i> (That is, if such a related package is available in selected repos.)
</I>>><i>
</I>>><i> Think of the gstreamer packages -- the "ugly" perhaps corresponding to the
</I>>><i> "constrained" packages being considered.
</I>>><i>
</I>>><i> my 2 cents :)
</I>>><i> --
</I>>><i> André
</I>>><i>
</I>><i>
</I>><i> Just a small note, if you didn't like the colour of the bike shed you
</I>><i> should have discussed the point before it was built, painted, the
</I>><i> paint has dried and is about to have new residents.
</I>><i>
</I>><i> And if you discussed the issue and your POV wasn't adapted, what's the
</I>><i> point re-emerging it now given that changing the new isn't easy now
</I>><i> that the infra- is already in place.
</I>
In 4+ months, a lot will be changed/corrected.
In my mind, this inappropriate name will tarnish Mageia.
We can surely find a much more appropriate name.
Since the repositories in question are empty, and will never be very
big, the cost of changing is minimal.
><i> I like the name tainted, (note that the kernel does use the word
</I>><i> tainted to indicate there's a non-open source binary blob/driver e.g.
</I>><i> with the nvidia proprietary driver, so this usage is not unheard of).
</I>><i> :)
</I>
And the word "tainted" wasn't used to indicate some kind of dysfunction
? (Normally the kernel outputs ERROR messages.)
I have encountered a kernel message containing "not tainted", to
indicate that a particular file was not corrupted. (The bug was caused
by something else.)
Regards :)
--
André
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="002760.html">[Mageia-dev] time to switch from raw partitions to lvm?
</A></li>
<LI>Next message: <A HREF="002781.html">[Mageia-dev] About panotools patent problem (and other problematic rpms)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#2761">[ date ]</a>
<a href="thread.html#2761">[ thread ]</a>
<a href="subject.html#2761">[ subject ]</a>
<a href="author.html#2761">[ 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>
|
