summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20101020/001325.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/20101020/001325.html')
-rw-r--r--zarb-ml/mageia-dev/20101020/001325.html128
1 files changed, 128 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101020/001325.html b/zarb-ml/mageia-dev/20101020/001325.html
new file mode 100644
index 000000000..bf8297523
--- /dev/null
+++ b/zarb-ml/mageia-dev/20101020/001325.html
@@ -0,0 +1,128 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Mirror tree structure
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20tree%20structure&In-Reply-To=%3C1287605174.3051.105.camel%40akroma.ephaone.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="001293.html">
+
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Mirror tree structure</H1>
+ <B>Michael Scherer</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20tree%20structure&In-Reply-To=%3C1287605174.3051.105.camel%40akroma.ephaone.org%3E"
+ TITLE="[Mageia-dev] Mirror tree structure">misc at zarb.org
+ </A><BR>
+ <I>Wed Oct 20 22:06:14 CEST 2010</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="001293.html">[Mageia-dev] Mirror tree structure
+</A></li>
+
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1325">[ date ]</a>
+ <a href="thread.html#1325">[ thread ]</a>
+ <a href="subject.html#1325">[ subject ]</a>
+ <a href="author.html#1325">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le mercredi 20 octobre 2010 &#224; 18:34 +0200, Olivier Thauvin a &#233;crit :
+&gt;<i> Hi,
+</I>&gt;<i>
+</I>&gt;<i> You can find here:
+</I>&gt;<i> <A HREF="http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/">http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/</A>
+</I>&gt;<i> the current mirror tree proposal.
+</I>&gt;<i> We now have to discuss it, I think.
+</I>&gt;<i>
+</I>&gt;<i> Here notes:
+</I>&gt;<i>
+</I>&gt;<i> The 'mageia_timestamp' is a file updated on the main server every 5
+</I>&gt;<i> minutes. It allow to check is a mirror synced or not
+</I>&gt;<i>
+</I>&gt;<i> Comparing to mandriva there is no more split between devel/stable, all
+</I>&gt;<i> distributions goes into distribs/ and all isos file into iso/.
+</I>&gt;<i>
+</I>&gt;<i> The updates/ tree disapear, avoiding some possible dependencies issues
+</I>&gt;<i> in updates rpms.
+</I>&gt;<i>
+</I>&gt;<i> The peoples/ directory is dedicated to contributors and must allow
+</I>&gt;<i> anyone to share files related to the distribution (testing rpms,
+</I>&gt;<i> preworks) in an unofficial ways.
+</I>&gt;<i> How this can be setup in practice still have to be discuss.
+</I>
+Like quota, etc ?
+
+&gt;<i> Finally the software/ directory should allow you to distribute the
+</I>&gt;<i> tarball (not rpm) for software we do. As soon we do free software people
+</I>&gt;<i> must be able to distribute our code in the same way any projects does.
+</I>&gt;<i> Replies like &quot;svn is readable&quot; or &quot;we have rpm&quot; is not appropriated.
+</I>&gt;<i>
+</I>&gt;<i> Now come the question: &quot;what is a valid mirror ?&quot;, eg, what a mirror
+</I>&gt;<i> should have as file to be valid ?
+</I>&gt;<i>
+</I>&gt;<i> I suggest to not give the choice and avoid mistake by saying except
+</I>&gt;<i> &quot;peoples&quot; a mirror must respect the whole tree to be valid.
+</I>
+I would also exclude software/ from regular mirror, because this may not
+requires as much redundancy than regular mirror ( ie, I doubt many
+people will download tarball on a regular basis, and most softwre
+project are fine with 2 or 3 mirror ).
+
+On the other hand, it may not add much overhead to mirrors anyway.
+
+
+Something I would like to add is database dumps ( cleaned from password
+and private information, of course ), and maybe svn backup, stuff like
+that. So people who wish to fork our project will not have the same
+problem as we did.
+
+One of the issue we currently have is the fact we couldn't fork Mandriva
+wiki, because we didn't have access to the server. The same goes for
+several components ( ideas, maintainers database, full bugzilla dump,
+etc ). One of my goal would be to have a forkable infrastructure, so
+people can replicate ours ( using puppet/cfengine, as we plan to use ).
+( replicate to study, replicate it to play with it, replicate to enhance
+it if needed )
+
+And this would also provides use with a &quot;linus t&quot; backup system :p
+
+
+&gt;<i> This mean everything must exists with this structure under the top level
+</I>&gt;<i> path.
+</I>&gt;<i> This way may avoid issues like mandriva on ibiblio (only 2005 and 2007.1
+</I>&gt;<i> seems to exists...)
+</I>&gt;<i> <A HREF="ftp://ibiblio.org/pub/linux/distributions/mandriva/Mandrivalinux/">ftp://ibiblio.org/pub/linux/distributions/mandriva/Mandrivalinux/</A>
+</I>
+I would let people choose what they mirror based on version. Ie, someone
+could mirror the last version only, the 3 last, etc, etc.
+
+This will likely provides enough flexibility without sacrifing too much
+the simplicity.
+--
+Michael Scherer
+
+</PRE>
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="001293.html">[Mageia-dev] Mirror tree structure
+</A></li>
+
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1325">[ date ]</a>
+ <a href="thread.html#1325">[ thread ]</a>
+ <a href="subject.html#1325">[ subject ]</a>
+ <a href="author.html#1325">[ 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>