diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101127/001443.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101127/001443.html | 131 |
1 files changed, 131 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101127/001443.html b/zarb-ml/mageia-dev/20101127/001443.html new file mode 100644 index 000000000..cf065b27d --- /dev/null +++ b/zarb-ml/mageia-dev/20101127/001443.html @@ -0,0 +1,131 @@ +<!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=%3C201011270044.29973.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="001442.html"> + <LINK REL="Next" HREF="001444.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=%3C201011270044.29973.maarten.vanraes%40gmail.com%3E" + TITLE="[Mageia-dev] Mirror layout, round two">maarten.vanraes at gmail.com + </A><BR> + <I>Sat Nov 27 00:44:29 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001442.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI>Next message: <A HREF="001444.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1443">[ date ]</a> + <a href="thread.html#1443">[ thread ]</a> + <a href="subject.html#1443">[ subject ]</a> + <a href="author.html#1443">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op zaterdag 27 november 2010 00:25:17 schreef Thomas Backlund: +[...] +><i> > A) i see no reason for codecs and firmware to be separate. However, i do +</I>><i> > understand that some people would not want to install firmware, but i +</I>><i> > think we should do this in another way, (like installing a meta package +</I>><i> > that enforces some limits.) +</I>><i> > codecs seem odd to be separate, if they have patented problems they +</I>><i> > should go in non_free, if no problem, they can go in core. +</I>><i> +</I>><i> That is doable. +</I>><i> The reason for having it separate was because its the most "problematic" +</I>><i> one. (codecs have more issues than firmware) +</I> +What i meant here, is why is firmware separate from core? why is codecs +separate from core? + +imo, i would put firmware and codecs in either core or non_free. + +><i> > B) if they are separate, they would need updates, backports, testing, ... +</I>><i> > (i expect non_free does too?) +</I>><i> +</I>><i> Yep. +</I>><i> as noted in the other post, the layout under /core/ is duplicated under +</I>><i> all other medias... +</I> +yeah, I only read your other post after writing this. + +><i> > C) if they are separate, they cannot be disabled by default, some stuff +</I>><i> > is needed for stuff to work. +</I>><i> +</I>><i> So installer could ask "in order to fully support your hw you need ..., +</I>><i> do you want to enable firmware repo..." and explain the reason for +</I>><i> free/libre... +</I> +that sounds like a good idea, however; do we have the time to change this in +the installer? + +><i> > D) i have questions about noarch packages, will they be installed on both +</I>><i> > trees? and if we have more archs later on, more and more? this seems a +</I>><i> > waste; except if we could hardlink them somehow. if not, we should just +</I>><i> > put them somewhere separate. +</I>><i> +</I>><i> We hardlink them already. +</I>><i> But yeah, I'd like a separate noarch too, but some people disagree, so I +</I>><i> didnt add it to this proposal. +</I> +well, especially when we get more archs, we really should separate noarchs; +i'm kind of feeling strong about this. + +><i> > E) i understand games to be separate, but disabled by default?, i'm not +</I>><i> > sure i agree with that. (we need to remember our target audience; stuff +</I>><i> > needs to work out-of the box) +</I>><i> +</I>><i> I was thinking of a feature in the installer, if you select games, it +</I>><i> would enable the repo by default, otherwise keep it disabled. +</I> +same as with C) . do we have the time for this? + +><i> > F) what is backports_testing? why can't that just be testing? +</I>><i> +</I>><i> Versioning problem... on mirrors / BS +</I>><i> we have testing -> updates route, +</I>><i> so this would be backports_testing -> backports, +</I>><i> +</I>><i> Because if you have this: +</I>><i> core/release v 1.2.0-1 +</I>><i> core/testing v 1.3.0-1 (intended for backports) +</I>><i> +</I>><i> then you cant upload a bugfix v 1.2.0-1.1 to core/testing as there is +</I>><i> already a bigger version in testing... +</I> +aah, makes sense. + +PS: i like the extra btw: (which should contain all unmaintained packages that +actually build) +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001442.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI>Next message: <A HREF="001444.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1443">[ date ]</a> + <a href="thread.html#1443">[ thread ]</a> + <a href="subject.html#1443">[ subject ]</a> + <a href="author.html#1443">[ 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> |