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
|
<!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=%3C201106291056.31260.anaselli%40linux.it%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="006111.html">
<LINK REL="Next" HREF="006115.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Proposal of a backporting process</H1>
<B>Angelo Naselli</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20of%20a%20backporting%20process&In-Reply-To=%3C201106291056.31260.anaselli%40linux.it%3E"
TITLE="[Mageia-dev] Proposal of a backporting process">anaselli at linux.it
</A><BR>
<I>Wed Jun 29 10:56:27 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="006111.html">[Mageia-dev] Proposal of a backporting process
</A></li>
<LI>Next message: <A HREF="006115.html">[Mageia-dev] Proposal of a backporting process
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6114">[ date ]</a>
<a href="thread.html#6114">[ thread ]</a>
<a href="subject.html#6114">[ subject ]</a>
<a href="author.html#6114">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>mercoledì 29 giugno 2011 alle 00:23, andre999 ha scritto:
><i> A leaf package is a package that is not required by any other package.
</I>><i> But leaf packages will always require something else.
</I>><i> If B requires A, then A is not a leaf package, even though B could be.
</I>><i> When backporting B, we test to make sure that it works with release A.
</I>><i> Obviously it restricts what can be backported, but the trade-off is that backports will
</I>><i> (almost always) work, and they won't break anything.
</I>
Well my point is i often backport something for my job (for the most
commoncpp2 now, ucommon in future), and since they are libraries i can fall
in errors. I always tested before backporting though, and i haven't had any problems
upgrading, but that's me and i could have been lucky.
If we can accept some exceptions from time to time, but proved (bug open, testing
and updates/backports etc) i can think to have mageia not only at home or in a virtual
box. Otherwise i can't see the need of backports, for me of course.
Angelo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/mageia-dev/attachments/20110629/3ac985d8/attachment.asc>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="006111.html">[Mageia-dev] Proposal of a backporting process
</A></li>
<LI>Next message: <A HREF="006115.html">[Mageia-dev] Proposal of a backporting process
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6114">[ date ]</a>
<a href="thread.html#6114">[ thread ]</a>
<a href="subject.html#6114">[ subject ]</a>
<a href="author.html#6114">[ 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>
|
