diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101127/001439.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101127/001439.html | 163 |
1 files changed, 163 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101127/001439.html b/zarb-ml/mageia-dev/20101127/001439.html new file mode 100644 index 000000000..bdb105a19 --- /dev/null +++ b/zarb-ml/mageia-dev/20101127/001439.html @@ -0,0 +1,163 @@ +<!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=%3C4CF03C27.1080208%40iki.fi%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + + <LINK REL="Next" HREF="001440.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Mirror layout, round two</H1> + <B>Thomas Backlund</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout%2C%20round%20two&In-Reply-To=%3C4CF03C27.1080208%40iki.fi%3E" + TITLE="[Mageia-dev] Mirror layout, round two">tmb at iki.fi + </A><BR> + <I>Sat Nov 27 00:00:55 CET 2010</I> + <P><UL> + + <LI>Next message: <A HREF="001440.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1439">[ date ]</a> + <a href="thread.html#1439">[ thread ]</a> + <a href="subject.html#1439">[ subject ]</a> + <a href="author.html#1439">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Renaud MICHEL skrev 26.11.2010 23:43: +><i> On vendredi 26 novembre 2010 at 21:29, Thomas Backlund wrote : +</I>>><i> Then we come to the "problematic" part: +</I>>><i> ------ +</I>>><i> x86_64 +</I>>><i> media +</I>>><i> codecs (disabled by default) +</I>>><i> core (old main+contrib) +</I>>><i> backports (disabled by default) +</I>>><i> backports_testing (disabled by default) +</I>>><i> release +</I>>><i> testing (disabled by default) +</I>>><i> updates +</I>>><i> extra (unmaintained, disabled by default) +</I>>><i> firmware (disabled by default) +</I>>><i> games (disabled by default) +</I>>><i> non-free (disabled by default) +</I>>><i> /debug_*/ (disabled by default) +</I>>><i> ----- +</I>>><i> +</I>>><i> The idea of this layout with some of the separate sections (codecs, +</I>>><i> firmware, games, non-free, debug_*) gives a mirror maintainer in a +</I>>><i> country (or company) the option to exclude the parts they legally (or by +</I>>><i> company policy) can not mirror. +</I>>><i> +</I>>><i> The "core" should be only maintained free/libre stuff so it's easy to +</I>>><i> build a free/libre iso +</I>>><i> +</I>>><i> "extra" is for those packages that no-one really maintain, but is still +</I>>><i> used by someone +</I>>><i> +</I>>><i> "games" are now a separate repo since it can grow fast with a lot of +</I>>><i> game data. +</I>><i> +</I>><i> I think it is a good layout, but, are updates/backports(testing) limited to +</I>><i> core? +</I>><i> +</I> +nope, the same layout: +backports (disabled by default) +backports_testing (disabled by default) +release +testing (disabled by default) +updates + +should be under codecs, extra, firmware, games, non-free, debug_* +in order to provide consistency betwen medias. +I just left them out because they was supposed to be the same for all. + +><i> As you mentioned, extra has no reason to have updates or backports, because +</I>><i> if someone did bother to make updates, then the package doesn't belong in +</I>><i> extra. +</I>><i> +</I> +Yeah, but for a stable release, we dont move packages... + +the /release/ must stay frozen. + +><i> For games it would surely be appreciated to have new versions, so maybe a +</I>><i> only a games/updates media which could also be used as a backport media (as +</I>><i> games are not critical). +</I>><i> +</I> +To simplify for all users, the medias should be used in the same way. + +><i> For non-free we would probably want also updates and backports, like in +</I>><i> current mandriva. +</I>><i> +</I> +yep. + +><i> Now for firmware and codecs I don't know, are there updates for firmwares? +</I> +Not often, but sometimes there are firmwares that get bugfixes, so the +same rule apply. + +><i> Maybe they should be in sync with kernel updates (or external modules)? +</I> +They must of course stay compatible with the kernel. + +><i> As for codecs, will it contain anything that could be covered by patents, +</I>><i> like PLF for mandriva? +</I>><i> Does that mean we will still have a stripped down mplayer/xine in core and a +</I>><i> full version in codecs? +</I> +This is one of the tricky ones... + +><i> But if it is only disabled and you only need to activate it in the control +</I>><i> center to have full featured multimedia programs, it is no big deal, and if +</I>><i> it makes life easier for people whose countries have restrictive law then +</I>><i> we should go for it. +</I>><i> +</I> +That was the idea. + +><i> We should probably have a clear rule to decide what cannot go in core and +</I>><i> should in non-free (that on is pretty clear already) codecs or firmware. +</I>><i> +</I> +yep. + +><i> I hope we will soon get to the point where we will actually put packages in +</I>><i> those repositories :-) +</I>><i> +</I> +we are getting closer... + +-- +Thomas +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + + <LI>Next message: <A HREF="001440.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1439">[ date ]</a> + <a href="thread.html#1439">[ thread ]</a> + <a href="subject.html#1439">[ subject ]</a> + <a href="author.html#1439">[ 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> |