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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Proposal of a backporting process
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20of%20a%20backporting%20process&In-Reply-To=%3C4E0A5453.90605%40laposte.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="006103.html">
<LINK REL="Next" HREF="006114.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Proposal of a backporting process</H1>
<B>andre999</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20of%20a%20backporting%20process&In-Reply-To=%3C4E0A5453.90605%40laposte.net%3E"
TITLE="[Mageia-dev] Proposal of a backporting process">andr55 at laposte.net
</A><BR>
<I>Wed Jun 29 00:23:15 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="006103.html">[Mageia-dev] Proposal of a backporting process
</A></li>
<LI>Next message: <A HREF="006114.html">[Mageia-dev] Proposal of a backporting process
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6111">[ date ]</a>
<a href="thread.html#6111">[ thread ]</a>
<a href="subject.html#6111">[ subject ]</a>
<a href="author.html#6111">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Angelo Naselli a écrit :
><i> domenica 26 giugno 2011 alle 13:38, Michael Scherer ha scritto:
</I>>><i> See the thread about policy, and the part about "only packages that
</I>>><i> nothing requires should be backported".
</I>><i> I can't see very well the leaf story... I mean any packages
</I>><i> require something at least to build. Scripts need interpreters, so
</I>><i> i'd expect interpreters cannot be backported, but we can find a
</I>><i> script based package (using perl, ruby or python...) needing some other
</I>><i> script based one, the same could happen for programs. Now what can
</I>><i> we backport there?
</I>><i> A and B are leaves (?) but B uses A so i can revert A for a problem,
</I>><i> now are we sure A on stable works with B on backports?
</I>><i>
</I>><i> Morever we could not backport new major libraries, they would not conflicts
</I>><i> with stable though, but sure they could affect some packages built in backports
</I>><i> after that should not work without new major.....
</I>><i>
</I>><i> I'm confused :/
</I>><i>
</I>><i> IMO we should improve the QA (or what else) and testing to allow a safe
</I>><i> installation and proving that will be upgraded to the next mageia release,
</I>><i> then if we call it backports, upgrades, updates or... that's
</I>><i> another and maybe less important thing.
</I>><i>
</I>><i> Angelo
</I>
A leaf package is a package that is not required by any other package.
But leaf packages will always require something else.
If B requires A, then A is not a leaf package, even though B could be.
When backporting B, we test to make sure that it works with release A.
Obviously it restricts what can be backported, but the trade-off is that backports will
(almost always) work, and they won't break anything.
--
André
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="006103.html">[Mageia-dev] Proposal of a backporting process
</A></li>
<LI>Next message: <A HREF="006114.html">[Mageia-dev] Proposal of a backporting process
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6111">[ date ]</a>
<a href="thread.html#6111">[ thread ]</a>
<a href="subject.html#6111">[ subject ]</a>
<a href="author.html#6111">[ 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>
|
