summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-November/009341.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2011-November/009341.html')
-rw-r--r--zarb-ml/mageia-dev/2011-November/009341.html163
1 files changed, 163 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-November/009341.html b/zarb-ml/mageia-dev/2011-November/009341.html
new file mode 100644
index 000000000..b74fee268
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-November/009341.html
@@ -0,0 +1,163 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Updating a new install is too long...
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Updating%20a%20new%20install%20is%20too%20long...&In-Reply-To=%3CCA%2Bh4nj7TqYYWRzsxpgBd6U1Nvjv5jUJV18sDy%2BRV6Co4rCs9EQ%40mail.gmail.com%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="009331.html">
+ <LINK REL="Next" HREF="009342.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Updating a new install is too long...</H1>
+ <B>Wolfgang Bornath</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Updating%20a%20new%20install%20is%20too%20long...&In-Reply-To=%3CCA%2Bh4nj7TqYYWRzsxpgBd6U1Nvjv5jUJV18sDy%2BRV6Co4rCs9EQ%40mail.gmail.com%3E"
+ TITLE="[Mageia-dev] Updating a new install is too long...">molch.b at googlemail.com
+ </A><BR>
+ <I>Sun Nov 6 08:15:12 CET 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="009331.html">[Mageia-dev] Updating a new install is too long...
+</A></li>
+ <LI>Next message: <A HREF="009342.html">[Mageia-dev] Updating a new install is too long...
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#9341">[ date ]</a>
+ <a href="thread.html#9341">[ thread ]</a>
+ <a href="subject.html#9341">[ subject ]</a>
+ <a href="author.html#9341">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>2011/11/5 Maarten Vanraes &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">alien at rmail.be</A>&gt;:
+&gt;<i> Op zaterdag 05 november 2011 16:24:17 schreef Pierre Jarillon:
+</I>&gt;<i> [...]
+</I>&gt;&gt;<i> Then it is too much to be stored in a cheap DVD.
+</I>&gt;&gt;<i> IMO, when the size of a branch reaches such a size, an updated release
+</I>&gt;&gt;<i> should be issued. Remember that a lot of people have a slow link to
+</I>&gt;&gt;<i> internet. Mandriva did such updated releases which all work better than
+</I>&gt;&gt;<i> the original, improving the confidence in the distro.
+</I>&gt;&gt;<i> Today, a woman who has installed Mageia alone and for the first time, said
+</I>&gt;&gt;<i> me that update is so much long that she thought the distro was broken.
+</I>&gt;<i> [...]
+</I>&gt;<i>
+</I>&gt;<i> If we were to use the updates directly when installing (ie: not install first
+</I>&gt;<i> then update, but use updated packages at install time), we could even say,
+</I>&gt;<i> have an &quot;Update CD/DVD&quot;, which just contains the packages in question and use
+</I>&gt;<i> that instead of eg: mirrors...
+</I>
+How is a download of a 600MB iso different from installing 600MB of
+updates via net? More, usually you will not need all updates, only
+updates of installed packages.
+
+&gt;<i> This would effectively solve the problem even when not rereleasing mageia. It's
+</I>&gt;<i> true that Mandriva did .0 and .1 but they also had yearly release and not
+</I>&gt;<i> 9months...
+</I>
+The .0 and .1 versions were always releases of their own. It was
+planned at some point in time to keep core packages for 12 months and
+just update userland packages in the .1-release. But that was never
+really carried through. Actually Mandriva did not release any &quot;update
+releases&quot; before 2010 (with exceptions). Until 2010.1 Mandriva had a
+6-months release cycle, 2010.2 was the first real &quot;update release&quot;
+(out of necessity because they could not provide a real release at
+that time of changes).
+
+One visible proof is: the .0 and .1 versions had their own complete,
+while 2010.2 just links to 2010.1 repos.
+
+The exceptions I mentioned above came in 2 cases where the normal
+release had critical bugs (driver for LG dvd drives, beta version of
+x-server). These update-releases did not get a different version, they
+did not use a new repo.
+
+As for update releases in general, I surely would like to see them.
+But I'm totally sure that there is no manpower available for that, not
+before Mageia 2 (all readers are invited to prove me wrong!). But I
+also see the option for local communities to make snapshots and send
+them to people with small bandwidth.
+
+--
+wobo
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="009331.html">[Mageia-dev] Updating a new install is too long...
+</A></li>
+ <LI>Next message: <A HREF="009342.html">[Mageia-dev] Updating a new install is too long...
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#9341">[ date ]</a>
+ <a href="thread.html#9341">[ thread ]</a>
+ <a href="subject.html#9341">[ subject ]</a>
+ <a href="author.html#9341">[ 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>