blob: 2687aad2025a14f081935361133ace0090934340 (
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
84
85
86
87
88
89
90
91
92
93
94
95
96
97
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Proposed Feature:Backports_update_applet
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposed%20Feature%3ABackports_update_applet&In-Reply-To=%3C20120612164641.GY21938%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="016465.html">
<LINK REL="Next" HREF="016265.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Proposed Feature:Backports_update_applet</H1>
<B>nicolas vigier</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposed%20Feature%3ABackports_update_applet&In-Reply-To=%3C20120612164641.GY21938%40mars-attacks.org%3E"
TITLE="[Mageia-dev] Proposed Feature:Backports_update_applet">boklm at mars-attacks.org
</A><BR>
<I>Tue Jun 12 18:46:41 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="016465.html">[Mageia-dev] Proposed Feature:UiAbstraction4mcc
</A></li>
<LI>Next message: <A HREF="016265.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16441">[ date ]</a>
<a href="thread.html#16441">[ thread ]</a>
<a href="subject.html#16441">[ subject ]</a>
<a href="author.html#16441">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Sat, 09 Jun 2012, andre999 wrote:
>><i>
</I>><i> You got me thinking :)
</I>><i> - Just marking all backport repos as update repos is almost enough to solve
</I>><i> the problem, in terms of the tools installing the backports. Great idea !
</I>><i> We just have to tweak the tools so that a backport is only installed as an
</I>><i> update of a backport.
</I>
No. People who only want to use a specific backport will not enable the
backport repository. They will install the backport and keep the
backports repository disabled.
><i>
</I>><i> - Note that we should allow a non-backport to replace a backport, as will
</I>><i> likely be encountered in a release update. If the versioning is properly
</I>><i> done (according to established packaging policy), a non-backport in a newer
</I>><i> release will have a higher version number, thus replacing the backport.
</I>
Which policy ?
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="016465.html">[Mageia-dev] Proposed Feature:UiAbstraction4mcc
</A></li>
<LI>Next message: <A HREF="016265.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16441">[ date ]</a>
<a href="thread.html#16441">[ thread ]</a>
<a href="subject.html#16441">[ subject ]</a>
<a href="author.html#16441">[ 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>
|