diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101127/001471.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101127/001471.html | 155 |
1 files changed, 155 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101127/001471.html b/zarb-ml/mageia-dev/20101127/001471.html new file mode 100644 index 000000000..e4e124341 --- /dev/null +++ b/zarb-ml/mageia-dev/20101127/001471.html @@ -0,0 +1,155 @@ +<!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=%3C201011272316.57088.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="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=%3C201011272316.57088.maarten.vanraes%40gmail.com%3E" + TITLE="[Mageia-dev] Mirror layout, round two">maarten.vanraes at gmail.com + </A><BR> + <I>Sat Nov 27 23:16:57 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001470.html">[Mageia-dev] Mirror layout, round two +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#1471">[ date ]</a> + <a href="thread.html#1471">[ thread ]</a> + <a href="subject.html#1471">[ subject ]</a> + <a href="author.html#1471">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op zaterdag 27 november 2010 22:07:43 schreef Michael scherer: +><i> On Sat, Nov 27, 2010 at 08:23:59PM +0200, Thomas Backlund wrote: +</I>><i> > Jerome Quelin skrev 27.11.2010 19:11: +</I>><i> > >On 10/11/27 17:59 +0100, Maarten Vanraes wrote: +</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/ +</I>><i> > will get moved to /extra/ as for a release the /core/ should only +</I>><i> > contain maintained packages. +</I>><i> +</I>><i> But isn't it in contradiction with the fact that release should not be +</I>><i> changed ? +</I>><i> +</I>><i> IE, a package could be in core for one release, and extras in another. +</I>><i> +</I>><i> What happen to such shrodingerian packages ? +</I>><i> What happen if this break the self containement ? +</I>><i> And finally, isn't it redoing contribs/main , leading in the future to the +</I>><i> same problem we tried to avoid ? +</I>><i> +</I>><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 +</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>><i> +</I>><i> And so, if no one step, wouldn't it be like current mdv, where people will +</I>><i> say they maintain the package just because someone has to do the job ? +</I>><i> +</I>><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> Then why don't we either : +</I>><i> - decide that non maintened package must be taken care by trainee, as +</I>><i> part of the training +</I>><i> - decide to clean them. +</I> +that's a great idea, we need more trainees! but of course, we can't do that +with all 5000+ unmaintained packages... + +is there a way to get rpm usage stats from those unmaintained packages. + +><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> +</I>><i> That's already what the GPL say, basically :) +</I>><i> ( you have no garantee of anything ). +</I>><i> +</I>><i> Yet, I fail to see what benefit it does really bring to users. Most of them +</I>><i> will enable the media ( because some people enable everything ), will +</I>><i> forget the message ( because we always forget popup, thanks +</I>><i> to endless abuse of such popup ), +</I>><i> and the only benefit is that we could tell "we told you". Not really +</I>><i> satisfying, and if I was a user, it would not really please me, nor +</I>><i> inspire confidence. +</I> +some would, but that they'd also enable testing, backports, debug, etc... if +they really do so, it's kind of their own fault. i don't think the majority +does that. the majority leaves it at default. + +The thing is that you have no guarantee, but the thing is, with mdv, there's +too much packages that just don't work; you install it, you click in the menu +and nothing happens because it doesn't work. if i have 2 packages that do the +same thing and one of them is in extra; then i get only one, if i can't find +any, i can enable the searching in extra and try to find a package that works. + +that's why i personally would prefer to leave these off by default. + +><i> We could avoid adding a media by merging this media with core, +</I>><i> and show the popup when a user install a package without maintainer, +</I>><i> telling either "beware, this package is currently marked as not maintained, +</I>><i> and may be buggy. We will try to do what we can to help in this case, but +</I>><i> no one is officialy in charge" or "we are seeking help on taking care of +</I>><i> this package, if you use it often, please register on $URL" +</I> +this popup will get ignored too; and persons who are perfectly aware of it, +will grow irritated. + +futhermore: (no separate extra) + - huge amount of packages (think of the mirrors) + - huge hdlists +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001470.html">[Mageia-dev] Mirror layout, round two +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#1471">[ date ]</a> + <a href="thread.html#1471">[ thread ]</a> + <a href="subject.html#1471">[ subject ]</a> + <a href="author.html#1471">[ 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> |