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
|
<!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%20management&In-Reply-To=%3C1286360454.15513.44.camel%40akroma.ephaone.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="000880.html">
<LINK REL="Next" HREF="000891.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Various proposals around backports and other media management</H1>
<B>Michael Scherer</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Various%20proposals%20around%20backports%20and%20other%20media%0A%20management&In-Reply-To=%3C1286360454.15513.44.camel%40akroma.ephaone.org%3E"
TITLE="[Mageia-dev] Various proposals around backports and other media management">misc at zarb.org
</A><BR>
<I>Wed Oct 6 12:20:54 CEST 2010</I>
<P><UL>
<LI>Previous message: <A HREF="000880.html">[Mageia-dev] Various proposals around backports and other media management
</A></li>
<LI>Next message: <A HREF="000891.html">[Mageia-dev] Various proposals around backports and other media management
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#883">[ date ]</a>
<a href="thread.html#883">[ thread ]</a>
<a href="subject.html#883">[ subject ]</a>
<a href="author.html#883">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le mardi 05 octobre 2010 à 23:06 +0100, Buchan Milne a écrit :
><i> On Tuesday, 5 October 2010 19:46:45 Samuel Verschelde wrote:
</I>
><i> > Some user communities already did that for 3rd party
</I>><i> > repositories for Mandriva, and having it in a centralized and visible
</I>><i> > place would make backports more visible. How many users know that latest
</I>><i> > versions for wine, wesnoth (one of the best opensource games), vlc, and
</I>><i> > many other packages are already available in backports media for mandriva
</I>><i> > ? Today there is a changelog mailing list, but this is not for everyone.
</I>><i> > This would be more user-centric than packager-centric. I tried to improve
</I>><i> > backports visibility on the Mandriva forum, but without any automation it
</I>><i> > took an enormous amount of time to maintain :
</I>><i> > <A HREF="http://forum.mandriva.com/viewforum.php?f=123">http://forum.mandriva.com/viewforum.php?f=123</A> (see threads beginning with
</I>><i> > "New Soft" or "Backport")
</I>><i>
</I>><i> RSS feed or use of twitter by build system may be useful ....
</I>
Youri already have RSS, afaik.
<A HREF="http://www.zarb.org/cgi-bin/viewvc.cgi/youri/soft/submit/trunk/lib/Youri/Submit/Step/Action/RSS.pm?revision=2100&view=markup">http://www.zarb.org/cgi-bin/viewvc.cgi/youri/soft/submit/trunk/lib/Youri/Submit/Step/Action/RSS.pm?revision=2100&view=markup</A>
Twitter/statusnet could be easy to add , according to
<A HREF="http://status.net/wiki/Libraries">http://status.net/wiki/Libraries</A> , this would quite trivial
I even think that a plugin to post on a forum could be done. A little
bit less trivial, but I am ok to work on it, once everything we have is
running.
><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>
We have solved the problem at PLF by forcing build to appear in cooker
first. It is just a youri plugin.
--
Michael Scherer
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000880.html">[Mageia-dev] Various proposals around backports and other media management
</A></li>
<LI>Next message: <A HREF="000891.html">[Mageia-dev] Various proposals around backports and other media management
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#883">[ date ]</a>
<a href="thread.html#883">[ thread ]</a>
<a href="subject.html#883">[ subject ]</a>
<a href="author.html#883">[ 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>
|
