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
111
112
113
114
115
116
117
118
119
120
121
122
123
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Mirror layout, round two
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout%2C%20round%20two&In-Reply-To=%3C201011272103.16544.maarten.vanraes%40gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="001468.html">
<LINK REL="Next" HREF="001470.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Mirror layout, round two</H1>
<B>Maarten Vanraes</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout%2C%20round%20two&In-Reply-To=%3C201011272103.16544.maarten.vanraes%40gmail.com%3E"
TITLE="[Mageia-dev] Mirror layout, round two">maarten.vanraes at gmail.com
</A><BR>
<I>Sat Nov 27 21:03:16 CET 2010</I>
<P><UL>
<LI>Previous message: <A HREF="001468.html">[Mageia-dev] Mirror layout, round two
</A></li>
<LI>Next message: <A HREF="001470.html">[Mageia-dev] Mirror layout, round two
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1469">[ date ]</a>
<a href="thread.html#1469">[ thread ]</a>
<a href="subject.html#1469">[ subject ]</a>
<a href="author.html#1469">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Op zaterdag 27 november 2010 19:23:59 schreef Thomas Backlund:
><i> Jerome Quelin skrev 27.11.2010 19:11:
</I>><i> > On 10/11/27 17:59 +0100, Maarten Vanraes wrote:
</I>><i> >> i agree, the less repositories the easier it'll be.
</I>><i> >>
</I>><i> >> however, core is for all the "maintained" packages, extra is for the
</I>><i> >> unmaintained packages that build ok.
</I>><i> >
</I>><i> > what is a "maintained" package? no maintainer, no commits since x
</I>><i> > months, not buildable? what if we move to packages being maintained by
</I>><i> > <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">foopkg at packages.mageia.org</A> aliases?
</I>><i>
</I>><i> if maintainer db says nomaintainer@ it belong in /extra/
</I>><i>
</I>><i> > what are the rules to move a package from extra to core, and vice-versa?
</I>><i> > who can do it? will it be done automatically? will this imply a rebuild
</I>><i> > for the package?
</I>><i>
</I>><i> If a maintainer picks up maintainership of a package in /extra/ it will
</I>><i> be rebuilt and moved to /core/ asap.
</I>><i>
</I>><i> if a package in /core/ ends up nomaintainer@, then after a "grace
</I>><i> period" (1-3 months ?) it will be moved to /extra/.
</I>><i> and sometime before RC1 or so, any momaintainer@ package in /core/ will
</I>><i> get moved to /extra/ as for a release the /core/ should only contain
</I>><i> maintained packages.
</I>
i would actually only move during cauldron freeze period (or right before it);
in both ways; so that the releases always stay the same for this kind of
thing.
><i> > what are the dependency rules? can a core package depend on an extra
</I>><i> > package? or with a buildrequires?
</I>><i>
</I>><i> No.
</I>><i> If you need to build against a package in /extra/, either pick up the
</I>><i> maintainership of it, or try to get someone other to maintain it.
</I>><i> then it can get into /core/
</I>
indeed, i would do this very strict; sometimes this might happen with some
kind of really core package, and then we'll have no choice but find a
maintainer for it; which is imho better.
><i> > and, more importantly: what is the advantage? that is, what does that
</I>><i> > bring you, except more admin?
</I>><i>
</I>><i> QA!
</I>><i> and enduser satisfaction.
</I>><i>
</I>><i> Just take a look on many bugreports in MDV Bugzilla.
</I>><i> If the report is against a nomaintainer@ package, currently Triage
</I>><i> pretty much only can state "thanks for your report, but since it has
</I>><i> no maintainer, nothing will probably happend" wich is not good answer
</I>><i> for a person that have taken the time to report a bug.
</I>><i>
</I>><i> By having the /extra/ disabled by default, and a popup notifying the
</I>><i> user if he enables it that the packages are "unmaintained" he knows
</I>><i> he's "on his own"
</I>
i agree
><i> > sorry, consider me not impressed by this idea. or maybe it's just that i
</I>><i> > failed to see the benefits. please enlighten me.
</I>><i>
</I>><i> --
</I>><i> Thomas
</I></PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="001468.html">[Mageia-dev] Mirror layout, round two
</A></li>
<LI>Next message: <A HREF="001470.html">[Mageia-dev] Mirror layout, round two
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1469">[ date ]</a>
<a href="thread.html#1469">[ thread ]</a>
<a href="subject.html#1469">[ subject ]</a>
<a href="author.html#1469">[ 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>
|
