diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101129/001493.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101129/001493.html | 192 |
1 files changed, 192 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101129/001493.html b/zarb-ml/mageia-dev/20101129/001493.html new file mode 100644 index 000000000..f922fa889 --- /dev/null +++ b/zarb-ml/mageia-dev/20101129/001493.html @@ -0,0 +1,192 @@ +<!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=%3C4CF3779C.5050403%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001500.html"> + <LINK REL="Next" HREF="001494.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Mirror layout, round two</H1> + <B>andre999</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout%2C%20round%20two&In-Reply-To=%3C4CF3779C.5050403%40laposte.net%3E" + TITLE="[Mageia-dev] Mirror layout, round two">andr55 at laposte.net + </A><BR> + <I>Mon Nov 29 10:51:24 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001500.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI>Next message: <A HREF="001494.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1493">[ date ]</a> + <a href="thread.html#1493">[ thread ]</a> + <a href="subject.html#1493">[ subject ]</a> + <a href="author.html#1493">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Michael scherer a écrit : +><i> On Sat, Nov 27, 2010 at 08:23:59PM +0200, Thomas Backlund wrote: +</I>><i> +</I>>><i> Jerome Quelin skrev 27.11.2010 19:11: +</I>>><i> +</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 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 same +</I>><i> problem we tried to avoid ? +</I>><i> +</I> +It's simply not workable to base a package's repository on whether it is +currently maintained or not. +It is much better to classify it on whether it *should* be maintained, +in order to have a fully functional user's system. +That is, it is in core because it is *core* to a typical fully +functional desktop or server or developer's system. Or very useful to +such a system. +So if such a package is not being properly maintained, there is a +collective focus to make sure that it is maintained, so that user's +systems remain functional. + +Extra should be just that. Packages that are extra to a fully +functional core Mageia system. + +It is inevitable that most packages, whatever their importance, will be +unmaintained - or at least without an official maintainer - from time to +time. +What we don't want to happen is a repository yoyo - where a package +bounces from core to main and back - just on the basis of its current +maintenance status. + +And a package should *never* change repositories between releases. +><i> +</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> +Seems like a lot of wasted effort - which could be better applied simply +maintaining core packages. +><i> And so, if no one step, wouldn't it be like current mdv, where people will say +</I>><i> they maintain the package just because someone has to do the job ? +</I>><i> +</I> +Note that Mandriva is currently overhauling their system - to remove +much non-core packages from main. +><i> +</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> +</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>><i> +</I> +Exactly. +>><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> +That's ridiculous. We should be in the cooperative spirit of the GPL, +instead of saying "too bad, you can't depend on Mageia." +><i> That's already what the GPL say, basically :) +</I>><i> ( you have no garantee of anything ). +</I>><i> +</I> +But no garantee doesn't mean no help. +><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 forget +</I>><i> 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 satisfying, +</I>><i> and if I was a user, it would not really please me, nor inspire confidence. +</I>><i> +</I>><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, and may +</I>><i> be buggy. We will try to do what we can to help in this case, but no one is officialy in charge" +</I>><i> or "we are seeking help on taking care of this package, if you use it often, please +</I>><i> register on $URL" +</I>><i> +</I>><i> +</I>Not a bad idea. Why not both messages ? +Really better than an option to exclude seeing officially non-maintained +packages. +Some packages on my system work perfectly well, but haven't been +"maintained" for several years. + +I would still keep a separate core and extra, where core is core, and +extra is extra. +(As I described above and in more detail in previous posts to this thread.) + +- André + +</PRE> + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001500.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI>Next message: <A HREF="001494.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1493">[ date ]</a> + <a href="thread.html#1493">[ thread ]</a> + <a href="subject.html#1493">[ subject ]</a> + <a href="author.html#1493">[ 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> |