summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20101127/001441.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/20101127/001441.html')
-rw-r--r--zarb-ml/mageia-dev/20101127/001441.html114
1 files changed, 114 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101127/001441.html b/zarb-ml/mageia-dev/20101127/001441.html
new file mode 100644
index 000000000..2cc43fcb0
--- /dev/null
+++ b/zarb-ml/mageia-dev/20101127/001441.html
@@ -0,0 +1,114 @@
+<!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=%3C201011270034.15839.r.h.michel%2Bmageia%40gmail.com%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="001457.html">
+ <LINK REL="Next" HREF="001452.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Mirror layout, round two</H1>
+ <B>Renaud MICHEL</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout%2C%20round%20two&In-Reply-To=%3C201011270034.15839.r.h.michel%2Bmageia%40gmail.com%3E"
+ TITLE="[Mageia-dev] Mirror layout, round two">r.h.michel+mageia at gmail.com
+ </A><BR>
+ <I>Sat Nov 27 00:34:15 CET 2010</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="001457.html">[Mageia-dev] Mirror layout, round two
+</A></li>
+ <LI>Next message: <A HREF="001452.html">[Mageia-dev] Mirror layout, round two
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1441">[ date ]</a>
+ <a href="thread.html#1441">[ thread ]</a>
+ <a href="subject.html#1441">[ subject ]</a>
+ <a href="author.html#1441">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On samedi 27 novembre 2010 at 00:02, Maarten Vanraes wrote :
+&gt;<i> C) if they are separate, they cannot be disabled by default, some stuff
+</I>&gt;<i> is needed for stuff to work.
+</I>
+I guess you are talking about firmware here.
+Maybe the installer could detect that a firmware is needed for some
+hardware, then it could either ask the user if he wants to enable the
+firmware repository, or automatically enable it.
+
+&gt;<i> D) i have questions about noarch packages, will they be installed on
+</I>&gt;<i> both trees? and if we have more archs later on, more and more? this
+</I>&gt;<i> seems a waste; except if we could hardlink them somehow. if not, we
+</I>&gt;<i> should just put them somewhere separate.
+</I>
+If the files are identical, they can be hard linked, and then the mirrors
+updates them with rsync -aH.
+(by the way, the readme already ask for those options
+<A HREF="http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/mirror.readme">http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/mirror.readme</A> )
+It is quite easy to make a script that will make those hard links &quot;&#224;
+posteriori&quot; (you only need to compare files with identical names)
+
+It could even be integrated into the build system (maybe it is already, I
+have no idea how it works), each time a noarch package is added to a
+repository it would check the corresponding repository for other arch if the
+same file is already present and is identical, and if so make a hard link
+instead of copying it.
+
+&gt;<i> E) i understand games to be separate, but disabled by default?, i'm not
+</I>&gt;<i> sure i agree with that. (we need to remember our target audience; stuff
+</I>&gt;<i> needs to work out-of the box)
+</I>
+This could also be decided at install time.
+If the user choose the game section then the games repository is enabled and
+some task-game-* are selected to install various games.
+
+&gt;<i> F) what is backports_testing? why can't that just be testing?
+</I>
+testing is for packages that will go to updates, backports_testing is for
+packages that will go to backports.
+I think it is likely that some people will be willing to test updates
+candidate but don't want to end up with backports, so enabling only testing
+and not backports_testing.
+
+If I remember correctly, there is currently (mdv2010.1 and previous) no
+testing stage for backported packages, and it was proposed during the
+discussion one month ago, that it would be good to have also a testing for
+backported packages.
+
+--
+Renaud Michel
+</PRE>
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="001457.html">[Mageia-dev] Mirror layout, round two
+</A></li>
+ <LI>Next message: <A HREF="001452.html">[Mageia-dev] Mirror layout, round two
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1441">[ date ]</a>
+ <a href="thread.html#1441">[ thread ]</a>
+ <a href="subject.html#1441">[ subject ]</a>
+ <a href="author.html#1441">[ 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>