blob: a6206cd902cb41f6e02d790e29b32d71854f8e5a (
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
|
<!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%09problematic%20rpms%29&In-Reply-To=%3C1b9a.4d618f25%40mageia.linuxtech.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="002691.html">
<LINK REL="Next" HREF="002693.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] About panotools patent problem (and other problematic rpms)</H1>
<B>Philippe DIDIER</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20About%20panotools%20patent%20problem%20%28and%20other%0A%09problematic%20rpms%29&In-Reply-To=%3C1b9a.4d618f25%40mageia.linuxtech.net%3E"
TITLE="[Mageia-dev] About panotools patent problem (and other problematic rpms)">philippedidier at laposte.net
</A><BR>
<I>Sun Feb 20 23:01:12 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="002691.html">[Mageia-dev] About panotools patent problem (and other problematic rpms)
</A></li>
<LI>Next message: <A HREF="002693.html">[Mageia-dev] So, you want to become a mageia packager
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#2692">[ date ]</a>
<a href="thread.html#2692">[ thread ]</a>
<a href="subject.html#2692">[ subject ]</a>
<a href="author.html#2692">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>
><i>Well, the old simple logic works...
</I>><i>
</I>><i>lets say we "abuse" the release tag, for example changing "mga" >to "mgt"
</I>><i>then if the user enables "tainted" (meaning he/she wants the >rpms) urpmi
</I>><i>will automatically get the "mgt" ones, no questions asked...
</I>><i>
</I>><i>simple, and effective.
</I>><i>
</I>><i>and since the rebuild should be automatically on our bs, the >versions
</I>><i>will stay in sync.
</I>
That seems to be the easyest compromise.
Allowing to use the existing spec files from mdv and plf with the least
modifications.
2 problems indeed :
for sysadmin point of view :
Is the BS able to build and dispatch two different versions of the same rpm
(core and tainted) ?
for the user
Is the package manager able to substitue simply a tainted rpm to a core rpm
if the tainted repos are selected ?
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="002691.html">[Mageia-dev] About panotools patent problem (and other problematic rpms)
</A></li>
<LI>Next message: <A HREF="002693.html">[Mageia-dev] So, you want to become a mageia packager
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#2692">[ date ]</a>
<a href="thread.html#2692">[ thread ]</a>
<a href="subject.html#2692">[ subject ]</a>
<a href="author.html#2692">[ 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>
|