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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Backports Summary
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20Summary&In-Reply-To=%3C20120627145704.GT21938%40mars-attacks.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="016926.html">
<LINK REL="Next" HREF="016938.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Backports Summary</H1>
<B>nicolas vigier</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20Summary&In-Reply-To=%3C20120627145704.GT21938%40mars-attacks.org%3E"
TITLE="[Mageia-dev] Backports Summary">boklm at mars-attacks.org
</A><BR>
<I>Wed Jun 27 16:57:04 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="016926.html">[Mageia-dev] Backports Summary
</A></li>
<LI>Next message: <A HREF="016938.html">[Mageia-dev] Backports Summary
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16929">[ date ]</a>
<a href="thread.html#16929">[ thread ]</a>
<a href="subject.html#16929">[ subject ]</a>
<a href="author.html#16929">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Wed, 27 Jun 2012, andre999 wrote:
><i> nicolas vigier a écrit :
</I>>><i> On Wed, 27 Jun 2012, andre999 wrote:
</I>>><i>
</I>>><i>
</I>>>>>><i> I would favour tagging backports as update repos, so that in the event
</I>>>>>><i> of a newer backport for security or bug fixes, that it will be
</I>>>>>><i> automatically presented with other updates.
</I>>>>>><i>
</I>>>>><i> No.
</I>>>>><i> as the update applet currently works it would show the backport as
</I>>>>><i> an update even if you dont have an earlier backport installed,
</I>>>>><i> defeating the purpose of having separate /updates vs /backports
</I>>>>><i>
</I>>>><i> This is conditional on first modifying the update tools, as suggested next.
</I>>>><i> A backport should only update an already installed backport.
</I>>>><i> (Similarly for nonfree and tainted, if that is not already the case.)
</I>>>><i>
</I>>><i> We should not change the behaviour of medias tagged as update repo. If
</I>>><i> we want a different behaviour for backports then we should tag those
</I>>><i> medias as backport, not update.
</I>>><i>
</I>><i>
</I>><i> The idea is, once the tools are appropriately adjusted, to tag the backport
</I>><i> repos as update media, as in rpmdrake. But alternately we could get the
</I>><i> update tools to automatically treat backport repos as update media for
</I>><i> backports.
</I>
backports are not updates, why should we tag them as update ?
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="016926.html">[Mageia-dev] Backports Summary
</A></li>
<LI>Next message: <A HREF="016938.html">[Mageia-dev] Backports Summary
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16929">[ date ]</a>
<a href="thread.html#16929">[ thread ]</a>
<a href="subject.html#16929">[ subject ]</a>
<a href="author.html#16929">[ 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>
|
