summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20101129/001519.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/20101129/001519.html')
-rw-r--r--zarb-ml/mageia-dev/20101129/001519.html146
1 files changed, 146 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101129/001519.html b/zarb-ml/mageia-dev/20101129/001519.html
new file mode 100644
index 000000000..cc03d6acc
--- /dev/null
+++ b/zarb-ml/mageia-dev/20101129/001519.html
@@ -0,0 +1,146 @@
+<!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=%3C4CF3F7A3.1010203%40laposte.net%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="001511.html">
+ <LINK REL="Next" HREF="001520.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=%3C4CF3F7A3.1010203%40laposte.net%3E"
+ TITLE="[Mageia-dev] Mirror layout, round two">andr55 at laposte.net
+ </A><BR>
+ <I>Mon Nov 29 19:57:39 CET 2010</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="001511.html">[Mageia-dev] Mirror layout, round two
+</A></li>
+ <LI>Next message: <A HREF="001520.html">[Mageia-dev] Mirror layout, round two
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1519">[ date ]</a>
+ <a href="thread.html#1519">[ thread ]</a>
+ <a href="subject.html#1519">[ subject ]</a>
+ <a href="author.html#1519">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>nicolas vigier a &#233;crit :
+&gt;<i> On Mon, 29 Nov 2010, Samuel Verschelde wrote:
+</I>&gt;<i>
+</I>&gt;<i>
+</I>&gt;&gt;<i> Indeed, however it helps showing that there's a set of packages which is supported, and another one which is only on behalf of the maintainer. In a community driven distribution, this distinction may remains valid : some packages are officially supported by the distribution, others may or may not be, depending on the maintainer (or lack of maintainer).
+</I>&gt;&gt;<i>
+</I>
+Exactly. And remember that the proposed restriction for core was those
+packages necessary to a typical desktop or server or development system,
+plus a *few* very useful/widely used packages such as LibreOffice
+(OpenOffice) and Firefox.
+Suggested to be included was &quot;complete desktops&quot;, which would be
+somewhat subjective as well.
+Outside of these potentially controversial borderline cases, what would
+be in core would be well defined.
+&gt;<i> We don't need separate medias to show that there are two sets of
+</I>&gt;<i> packages, supported and unsupported. I think using separate medias adds
+</I>&gt;<i> useless complexity.
+</I>If we look at our origins, we are not adding media here.
+But we are limiting what is in &quot;core&quot; (main).
+Note that in their reorganization, Mandriva is moving in the same direction.
+I see this more as a refocus of the packaging process, much like the
+(very useful) addition of backports_testing.
+
+&gt;<i> We could for instance provide a file on api.mageia.org
+</I>&gt;<i> containing the list of officially supported packages. It would also have
+</I>&gt;<i> other advantages :
+</I>&gt;<i> - You can see how many unsupported packages and which ones are installed
+</I>&gt;<i> on your system. This is not possible with main/contrib, if you enabled
+</I>&gt;<i> contrib temporarly to install a few packages.
+</I>&gt;<i>
+</I>
+This is not really related to one or 2 groups of repositories. Although
+doing that for *officially fully supported* packages should be
+moderately easier with separate groups.
+Note that many packages in &quot;extra&quot; would also be very well supported, by
+the packager or official maintainer.
+
+The idea is not that the Mageia community would not support &quot;extra&quot;
+packages.
+It is just that if an &quot;extra&quot; package breaks, it shouldn't break a
+user's system.
+But if a &quot;core&quot; package breaks, we would expect that it would break many
+users' systems.
+Thus the priority to ensure that &quot;core&quot; packages are always fixed in a
+timely manner.
+
+&gt;<i> - You can change the package status (supported/unsupported) after the
+</I>&gt;<i> release, if needed.
+</I>&gt;<i>
+</I>If the division is well defined, we should rarely need to change a
+package's status.
+There will be many well supported packages in &quot;extra&quot;.
+
+&gt;<i> - Some packages can have a different support time. On Mandriva, &quot;Base
+</I>&gt;<i> system&amp; components&quot; was supported longer, but it was not clear which
+</I>&gt;<i> packages were part of this.
+</I>&gt;<i>
+</I>Core is proposed to be largely &quot;base system &amp; components&quot;. Part of the
+idea is to make clearer, to everyone, which packages have an enhanced
+level of support.
+Support time is another (useful) question.
+
+&gt;<i> - This file could also list known security issues for unsupported
+</I>&gt;<i> and supported packages.
+</I>&gt;<i>
+</I>Not related to the core/extra question, but a useful feature. For
+Mageia-app-db project :)
+
+&gt;<i> - Some packages have a lot of optional plugins, and we build them all,
+</I>&gt;<i> adding a lot of build requires. With main/contrib separation we need
+</I>&gt;<i> to add all the build dependencies to main, even if most of them are
+</I>&gt;<i> not runtime dependencies.
+</I>&gt;<i>
+</I>
+We will have to be more selective for core packages, to avoid this problem.
+Maybe &quot;suggests&quot;, or other features being added with rpm5.
+
+I would agree that, at least in the transition, this would make more
+work for packagers.
+But in the longer term we will have a much more stable system.
+I see this as one of the key advantages of this &quot;core&quot; / &quot;extra&quot; separation.
+
+(Hopefully we will also get rid of annoyances such as requiring everyone
+to install thai localisations.)
+(Note that Mandriva is moving to rpm5 for their next full release
+(proposed for May 2011), which has more features for building rpms.
+Presumably Mageia will follow.)
+
+- Andr&#233;
+</PRE>
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="001511.html">[Mageia-dev] Mirror layout, round two
+</A></li>
+ <LI>Next message: <A HREF="001520.html">[Mageia-dev] Mirror layout, round two
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1519">[ date ]</a>
+ <a href="thread.html#1519">[ thread ]</a>
+ <a href="subject.html#1519">[ subject ]</a>
+ <a href="author.html#1519">[ 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>