diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101129/001522.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101129/001522.html | 150 |
1 files changed, 150 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101129/001522.html b/zarb-ml/mageia-dev/20101129/001522.html new file mode 100644 index 000000000..625b736c9 --- /dev/null +++ b/zarb-ml/mageia-dev/20101129/001522.html @@ -0,0 +1,150 @@ +<!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=%3C4CF41BCE.60606%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001520.html"> + <LINK REL="Next" HREF="001525.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=%3C4CF41BCE.60606%40laposte.net%3E" + TITLE="[Mageia-dev] Mirror layout, round two">andr55 at laposte.net + </A><BR> + <I>Mon Nov 29 22:31:58 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001520.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI>Next message: <A HREF="001525.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1522">[ date ]</a> + <a href="thread.html#1522">[ thread ]</a> + <a href="subject.html#1522">[ subject ]</a> + <a href="author.html#1522">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>nicolas vigier a écrit : +><i> On Mon, 29 Nov 2010, andre999 wrote: +</I>><i> +</I>><i> +</I>>><i> The idea is not that the Mageia community would not support "extra" +</I>>><i> packages. +</I>>><i> It is just that if an "extra" package breaks, it shouldn't break a user's +</I>>><i> system. +</I>>><i> But if a "core" package breaks, we would expect that it would break many +</I>>><i> users' systems. +</I>>><i> Thus the priority to ensure that "core" packages are always fixed in a +</I>>><i> timely manner. +</I>>><i> +</I>><i> I don't think we need repositories to define bug priorities. If a +</I>><i> package break the system, the bug report should mention it. And we can +</I>><i> also have minor bugs in "core" packages not breaking anything. Should +</I>><i> we fix them in a timely manner, before any critical bug on "extra" +</I>><i> packages breaking useful applications ? +</I>><i> +</I>I agree that minor bugs in core need not have absolute priority. +But from what I see, few bug reports mention that something "breaks the +system". +They focus on the issue in question, to varying degrees of success. +(Reminds me of end-user support. Much of the time they don't recognize +the real problem.) +My point is, significant bugs in core packages should be fixed in a +timely manner, as much as possible. And indeed, critical bugs should be +fixed. But if a critical bug affects a non-core package, it is likely +to affect only that package. Not so a core bug. + +By core, I mean in the logical sense. +If that can be done effectively and efficiently with a set of "core" +repositories, so be it. +However I don't see such a solution. +I would very much prefer to continue with the present separation until +such a solution, if any, is found. +And the cost of separate "core" and "extra" repositories is minimal, +assuming that core packages are officially supported. And separate +repositories do provide benefits to end-users, as well. +>>><i> - Some packages can have a different support time. On Mandriva, "Base +</I>>>><i> system& components" was supported longer, but it was not clear which +</I>>>><i> packages were part of this. +</I>>>><i> +</I>>>><i> +</I>>><i> Core is proposed to be largely "base system& components". Part of the +</I>>><i> idea is to make clearer, to everyone, which packages have an enhanced level +</I>>><i> of support. +</I>>><i> Support time is another (useful) question. +</I>>><i> +</I>><i> Why do we need two repositories for that ? +</I>><i> +</I>Sandbox. +It is clearer to everyone. +The fact that Mandriva didn't control what went into main is a large +part of their problem. +If you can find another solution, just as reliable, great. +But I suspect it would be more complex, and probably cost more in +resources as well. +The cost of extra repositories is almost nil - if we assume that we want +to rigorously control what is to be fully supported, and apply it. +>>><i> - Some packages have a lot of optional plugins, and we build them all, +</I>>>><i> adding a lot of build requires. With main/contrib separation we need +</I>>>><i> to add all the build dependencies to main, even if most of them are +</I>>>><i> not runtime dependencies. +</I>>>><i> +</I>>><i> We will have to be more selective for core packages, to avoid this problem. +</I>>><i> Maybe "suggests", or other features being added with rpm5. +</I>>><i> +</I>><i> Suggests on BuildRequires does not exists. And we need them to be +</I>><i> installed for the build. +</I>><i> +</I>If a core package has real buildrequires, then these requires should be +in core. +If only a non-core package has buildrequires, these requires need not +necessarily be in core. +Although packages like cmake should probably be in core anyway, as they +are very likely to be used to build packages. +I don't know details for rpm5, but it could have the equivalent of +suggests for buildrequires. (Like an alternate list of tools required ?) +Alternately, maybe some modification will have to be done to the spec files. +Since Mandriva is going through a very similar process, we could +probably share much of the changes required. + +By the way, for the conversion to Mageia, I would suggest assuming that +all of main + contrib is in extra, and moving those to core which meet +our criteria. +Much of main will be very quickly moved, such as base Linux/Gnu +packages, drak* tools, etc. +And selected applications like Go-oo/LibreOffice and Firefox. +We will first have to detail our criteria, of course. + +another 2 cents :) + +- André +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001520.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI>Next message: <A HREF="001525.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1522">[ date ]</a> + <a href="thread.html#1522">[ thread ]</a> + <a href="subject.html#1522">[ subject ]</a> + <a href="author.html#1522">[ 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> |