diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101129/001488.html')
-rw-r--r-- | zarb-ml/mageia-dev/20101129/001488.html | 131 |
1 files changed, 131 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101129/001488.html b/zarb-ml/mageia-dev/20101129/001488.html new file mode 100644 index 000000000..09b14989a --- /dev/null +++ b/zarb-ml/mageia-dev/20101129/001488.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=%3C1291000599.8266.44.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="001484.html"> + <LINK REL="Next" HREF="001489.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Mirror layout, round two</H1> + <B>Michael Scherer</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout%2C%20round%20two&In-Reply-To=%3C1291000599.8266.44.camel%40akroma.ephaone.org%3E" + TITLE="[Mageia-dev] Mirror layout, round two">misc at zarb.org + </A><BR> + <I>Mon Nov 29 04:16:39 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001484.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI>Next message: <A HREF="001489.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1488">[ date ]</a> + <a href="thread.html#1488">[ thread ]</a> + <a href="subject.html#1488">[ subject ]</a> + <a href="author.html#1488">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le lundi 29 novembre 2010 à 02:33 +0100, Maarten Vanraes a écrit : + +><i> > [ michael's long email ] +</I>><i> > +</I>><i> I agree with you partly (mostly on the basis that mirror setup should be +</I>><i> primarily for mirror admins), however: +</I>><i> - some of those big packages are pretty much core +</I> +The goal is not to place all big packages somewhere else. Just newer +packages that goes of the limit, even if they are not big. And by newer, +I mean "newer rpm", not "newer release of a existing packages". + +><i> - and a big core repos is having a big hdlists as well; and you should take +</I>><i> into consideration that some people have regular phone line internet. +</I> +Then, maybe a big index file is not a good idea. Using rsync + splitted +headers, like yum does, would maybe be more suitable for this situation +( nanar proposed this when we discussed of this some months ago while +eating pizza ). + +And in fact, bigger hdlists come from : +- having lots of package ( 10k by rpm, estimation of Olivier ) +- having lots of file ( 1k per file, same origin ) +- having lots of requires/provides ( even if this is likely negligible ) + +A package with a 100 mb file is taking less hdlist space ( around 10k ) +than a package with 100 files of 30k ( around 110k ). + +For exemple, on mandriva mirror, +kernel-kerriged-source header : 1.3mo, rpm 32 mo. +vegastrike-data header : 446ko, rpm 430 mo. + +And so, the explosion of kernel packages is likely a cause of contribs +hdlist size increase. On the 2010.1 stable mdv release, there is 28 +kernel or kernel-sources rpm, thus using around 28 mo in the 74 mo sized +hdlist, ie 33% ). + +Thus splitting games will not lead to a so big decrease of the hdlist. + + +><i> - i'm not entirely sure that mirror admins would like the overflow idea: +</I>><i> - if you're a small public mirror (ie: storage size), you would not mirror +</I>><i> the overflow; however some big packages would be pretty essential. seperating +</I>><i> extra (unmaintained packages); and games would seem easier; +</I> +Well, not mirroring is the goal of the overflow media, as explained. I +have already explained why games is not really a good idea, and why the +unmaintained idea is also not a good idea, so I will not repeat myself +( especially since you did it for me by not cleaning the mail before +responding :/ ). + +><i> also on the +</I>><i> following up side; (ie: when problems arise); also a point is what about those +</I>><i> big packages and their dependencies (or rather other packages which depend on +</I>><i> it). +</I> +That's why I said "there is no difference between core and overflow". +This mean "core can depend on overflow or core, overflow can depend on +core or overflow". And while a user could remove overflow, I do not +think one of the goal is to prevent people from doing stupid stuff +( like removing release, or disabling updates, for urpmi related +example ) + +><i> - i don't believe unmaintained packages is something that can be avoided +</I> +I do not think unmaintained packages is such a problem that everybody +seems to imply ( and the fact no one gave me any convincing stats or +data is not in favor of making me change my mind ). My own opinion is +that most people have seen on of their pet peeves not fixed because of +that, thus making the problem much more important in the eyes of each of +us than it is in reality. + +-- +Michael Scherer + +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001484.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI>Next message: <A HREF="001489.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1488">[ date ]</a> + <a href="thread.html#1488">[ thread ]</a> + <a href="subject.html#1488">[ subject ]</a> + <a href="author.html#1488">[ 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> |