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
|
<!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=%3Cb8687a3bb138a1a91aaca9b7f4e65177%40www.ephaone.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="002662.html">
<LINK REL="Next" HREF="002668.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] About panotools patent problem (and other problematic rpms)</H1>
<B>Michael Scherer</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=%3Cb8687a3bb138a1a91aaca9b7f4e65177%40www.ephaone.org%3E"
TITLE="[Mageia-dev] About panotools patent problem (and other problematic rpms)">misc at zarb.org
</A><BR>
<I>Sat Feb 19 14:59:46 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="002662.html">[Mageia-dev] About panotools patent problem (and other problematic rpms)
</A></li>
<LI>Next message: <A HREF="002668.html">[Mageia-dev] About panotools patent problem (and other problematic rpms)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#2665">[ date ]</a>
<a href="thread.html#2665">[ thread ]</a>
<a href="subject.html#2665">[ subject ]</a>
<a href="author.html#2665">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE> On Sat, 19 Feb 2011 09:20:50 +0100, Maarten Vanraes wrote:
><i> Op vrijdag 18 februari 2011 14:42:02 schreef Michael Scherer:
</I>>><i> Le vendredi 18 février 2011 à 12:47 +0000, James Kerr a écrit :
</I>>><i> > If there are two packages, one in core and another in tainted,
</I>>><i> then
</I>>><i> > doesn't urpmi need a way to recognise that the tainted package is
</I>>><i> newer
</I>>><i> > than (an update to) the corresponding core package? I believe that
</I>>><i> this
</I>>><i> > is achieved in Mandriva, because plf is greater than mdv.
</I>>><i>
</I>>><i> That's abusing release tag and it work by pure chance ( ie, had the
</I>>><i> plf
</I>>><i> decided to be called the guillomovitch liberation front, it would
</I>>><i> not
</I>>><i> have worked ). And this is quite inflexible, since people will
</I>>><i> always
</I>>><i> have plf packages, leading to users adding some rpm in skip.list
</I>>><i> with a
</I>>><i> regexp.
</I>>><i>
</I>>><i> This doesn't make much sense to treat tainted rpm as update to core,
</I>>><i> this is not the same notion. But we cannot express this in urpmi for
</I>>><i> the
</I>>><i> moment, as this would requires some way to say "if you need to
</I>>><i> install
</I>>><i> something, prefer this source rather than this one".
</I>>><i>
</I>>><i> We can imagine a priority system, or we can simply say that if there
</I>>><i> is
</I>>><i> the same rpm on 2 media, we ask to the user ( except this would
</I>>><i> requires
</I>>><i> IMHO a better system than the current path based one to see what is
</I>>><i> in a
</I>>><i> rpm, but that's a rather long proposal to make ).
</I>>><i>
</I>>><i> But you are right this another set of issues to solve for dual life
</I>>><i> packages.
</I>><i>
</I>><i> after sleeping on this, i've had this idea:
</I>><i>
</I>><i> why don't we rename packages in tainted?
</I>><i> keeping them in the same name, perhaps has issues with search
</I>><i> engines, (ie:
</I>><i> which version do you get?)
</I>
with search engine ?
I can see the issue for support, yes, but search engine, no
><i> i proposed renaming packages in tainted,(but not the release tag).
</I>><i>
</I>><i> would it be a good compromise if we named packages:
</I>><i>
</I>><i> <orig_packagename>-tainted-<version>-<release> ?
</I>><i>
</I>><i> the benefit of this could be adding an Obsoletes and Provides on the
</I>><i> original
</I>><i> package with the identical version.
</I>
This could work, but I am not sure that a Obsoletes is required.
One problem with this idea is that it will ask to user lots of
questions, and that's
something we should rather try to avoid ( any people who installed some
java rpm will
understand the issue ).
But it has the advantage of not requiring anything special on BS while
providing the choice.
><i> for building, i may have this solution:
</I>><i>
</I>><i> %tainted(%_optional_feature1 %optional_feature2 %optional_feature3)
</I>><i>
</I>><i> this would allow the buildbot to look for %tainted and if it does,
</I>><i> it could
</I>><i> rebuild it for tainted and add the particulars itself. this would
</I>><i> simplify the
</I>><i> whole plf/tainted thing easily. and since all 4 rpms are being built
</I>><i> at the
</I>><i> same time, you have no srpm problem either.
</I>
A simple %define would do the trick, so that doesn't bring much.
And we can keep a list of package that should be compiled twice, that's
not the biggest problem to solve.
--
Michael Scherer
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="002662.html">[Mageia-dev] About panotools patent problem (and other problematic rpms)
</A></li>
<LI>Next message: <A HREF="002668.html">[Mageia-dev] About panotools patent problem (and other problematic rpms)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#2665">[ date ]</a>
<a href="thread.html#2665">[ thread ]</a>
<a href="subject.html#2665">[ subject ]</a>
<a href="author.html#2665">[ 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>
|
