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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Various proposals around backports and other media management
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Various%20proposals%20around%20backports%20and%20other%20media%0A%09management&In-Reply-To=%3C201010060944.37256.stormi%40laposte.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="000876.html">
<LINK REL="Next" HREF="000883.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Various proposals around backports and other media management</H1>
<B>Samuel Verschelde</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Various%20proposals%20around%20backports%20and%20other%20media%0A%09management&In-Reply-To=%3C201010060944.37256.stormi%40laposte.net%3E"
TITLE="[Mageia-dev] Various proposals around backports and other media management">stormi at laposte.net
</A><BR>
<I>Wed Oct 6 09:44:37 CEST 2010</I>
<P><UL>
<LI>Previous message: <A HREF="000876.html">[Mageia-dev] Various proposals around backports and other media management
</A></li>
<LI>Next message: <A HREF="000883.html">[Mageia-dev] Various proposals around backports and other media management
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#880">[ date ]</a>
<a href="thread.html#880">[ thread ]</a>
<a href="subject.html#880">[ subject ]</a>
<a href="author.html#880">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>
Le mercredi 6 octobre 2010 00:06:41, Buchan Milne a écrit :
><i>
</I>><i> On Tuesday, 5 October 2010 19:46:45 Samuel Verschelde wrote:
</I>><i> > - a section on the mageia website dedicated to package updates : what's new
</I>><i> > in security/bugfix updates, what's new in backports (aka version updates),
</I>><i> > ... with screen captures, description of what changed in this version,
</I>><i> > links to upstream websites, comments from users, focus on some
</I>><i> > applications...
</I>><i>
</I>><i> Please take into consideration features that might be beneficial to package
</I>><i> maintainers as well. If you haven't yet, please look at e.g. Youri project,
</I>><i> Sophie etc.
</I>
The one I'm talking about would be primarily geared towards end-users. However, why not indeed share efforts between packager's needs and user's needs. Some are common, others aren't. With a clever architecture, this is attainable. What about a unique back-end, but 2 different frontends ?
><i>
</I>><i> RSS feed or use of twitter by build system may be useful ....
</I>
Indeed. I thought about them but forgot to write them down.
><i> > - (the biggest part, but the one with most long term benefits I hope) add
</I>><i> > metadata to media to make urpmi more media-aware. Today, rpmdrake detects
</I>><i> > backports because the backports media have "backports" in their name.
</I>><i> > That's a (useful) hack, but we could do better. One solution could be to
</I>><i> > give metadata to each media : * release vs updates vs backports
</I>><i> > * testing vs stable
</I>><i> > * debug vs non-debug
</I>><i> > Combination of these "tags" would give the following media :
</I>><i> > * main release (just like today's media)
</I>><i> > * main updates
</I>><i> > * main updates testing : for update candidates, this is our current
</I>><i> > "main testing" media * main backports
</I>><i> > * main backports testing : for backports candidates (as someone who
</I>><i> > frequently does backports, I sometimes feel the lack for it)
</I>><i>
</I>><i> As long as it doesn't take the focus off the development release. In Mandriva,
</I>><i> I think there were some uploads to backports before the upload to cooker,
</I>><i> which can cause problems for users if not corrected.
</I>
Indeed. I think that the current policy already tries to enforce that. Those uploads to backports before upload to cooker were mistakes.
I don't think that this media structure would change many things in the way that we packagers work, however. Benefits should be mainly for users.
Samuel
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000876.html">[Mageia-dev] Various proposals around backports and other media management
</A></li>
<LI>Next message: <A HREF="000883.html">[Mageia-dev] Various proposals around backports and other media management
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#880">[ date ]</a>
<a href="thread.html#880">[ thread ]</a>
<a href="subject.html#880">[ subject ]</a>
<a href="author.html#880">[ 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>
|
