diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101127/001470.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101127/001470.html | 137 |
1 files changed, 137 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101127/001470.html b/zarb-ml/mageia-dev/20101127/001470.html new file mode 100644 index 000000000..2afe31593 --- /dev/null +++ b/zarb-ml/mageia-dev/20101127/001470.html @@ -0,0 +1,137 @@ +<!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=%3C20101127210743.GA2419%40sisay.ephaone.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001469.html"> + <LINK REL="Next" HREF="001471.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Mirror layout, round two</H1> + <B>Michael scherer</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout%2C%20round%20two&In-Reply-To=%3C20101127210743.GA2419%40sisay.ephaone.org%3E" + TITLE="[Mageia-dev] Mirror layout, round two">misc at zarb.org + </A><BR> + <I>Sat Nov 27 22:07:43 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001469.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI>Next message: <A HREF="001471.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1470">[ date ]</a> + <a href="thread.html#1470">[ thread ]</a> + <a href="subject.html#1470">[ subject ]</a> + <a href="author.html#1470">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Sat, Nov 27, 2010 at 08:23:59PM +0200, Thomas Backlund wrote: +><i> Jerome Quelin skrev 27.11.2010 19:11: +</I>><i> >On 10/11/27 17:59 +0100, Maarten Vanraes wrote: +</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> +</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/ +</I>><i> will get moved to /extra/ as for a release the /core/ should only +</I>><i> contain maintained packages. +</I> +But isn't it in contradiction with the fact that release should not be changed ? + +IE, a package could be in core for one release, and extras in another. + +What happen to such shrodingerian packages ? +What happen if this break the self containement ? +And finally, isn't it redoing contribs/main , leading in the future to the same +problem we tried to avoid ? + +><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> +</I>><i> No. +</I>><i> If you need to build against a package in /extra/, either pick up +</I>><i> the maintainership of it, or try to get someone other to maintain +</I>><i> it. +</I>><i> then it can get into /core/ +</I> +And so, if no one step, wouldn't it be like current mdv, where people will say +they maintain the package just because someone has to do the job ? + +><i> >and, more importantly: what is the advantage? that is, what does that +</I>><i> >bring you, except more admin? +</I>><i> > +</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> +Then why don't we either : +- decide that non maintened package must be taken care by trainee, as +part of the training +- decide to clean them. + +><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> +That's already what the GPL say, basically :) +( you have no garantee of anything ). + +Yet, I fail to see what benefit it does really bring to users. Most of them +will enable the media ( because some people enable everything ), will forget +the message ( because we always forget popup, thanks +to endless abuse of such popup ), +and the only benefit is that we could tell "we told you". Not really satisfying, +and if I was a user, it would not really please me, nor inspire confidence. + +We could avoid adding a media by merging this media with core, +and show the popup when a user install a package without maintainer, +telling either "beware, this package is currently marked as not maintained, and may +be buggy. We will try to do what we can to help in this case, but no one is officialy in charge" +or "we are seeking help on taking care of this package, if you use it often, please +register on $URL" + +-- +Michael Scherer +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001469.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI>Next message: <A HREF="001471.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1470">[ date ]</a> + <a href="thread.html#1470">[ thread ]</a> + <a href="subject.html#1470">[ subject ]</a> + <a href="author.html#1470">[ 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> |