summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20101007/000942.html
diff options
context:
space:
mode:
authorNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
committerNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
commit1be510f9529cb082f802408b472a77d074b394c0 (patch)
treeb175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/20101007/000942.html
parentfa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff)
downloadarchives-master.tar
archives-master.tar.gz
archives-master.tar.bz2
archives-master.tar.xz
archives-master.zip
Add zarb MLs html archivesHEADmaster
Diffstat (limited to 'zarb-ml/mageia-dev/20101007/000942.html')
-rw-r--r--zarb-ml/mageia-dev/20101007/000942.html142
1 files changed, 142 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101007/000942.html b/zarb-ml/mageia-dev/20101007/000942.html
new file mode 100644
index 000000000..3c08b2125
--- /dev/null
+++ b/zarb-ml/mageia-dev/20101007/000942.html
@@ -0,0 +1,142 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] How will be the realese cycle?
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3C4CAD2E2D.6010801%40laposte.net%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="000956.html">
+ <LINK REL="Next" HREF="000943.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] How will be the realese cycle?</H1>
+ <B>andr&#233;</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3C4CAD2E2D.6010801%40laposte.net%3E"
+ TITLE="[Mageia-dev] How will be the realese cycle?">andr55 at laposte.net
+ </A><BR>
+ <I>Thu Oct 7 04:19:25 CEST 2010</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="000956.html">[Mageia-dev] How will be the realese cycle?
+</A></li>
+ <LI>Next message: <A HREF="000943.html">[Mageia-dev] How will be the realese cycle?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#942">[ date ]</a>
+ <a href="thread.html#942">[ thread ]</a>
+ <a href="subject.html#942">[ subject ]</a>
+ <a href="author.html#942">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Tux99 a &#233;crit :
+&gt;<i> On Tue, 5 Oct 2010, Thierry Vignaud wrote:
+</I>&gt;<i>
+</I>&gt;<i>
+</I>&gt;&gt;<i> On 5 October 2010 15:28, Tux99&lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">tux99-mga at uridium.org</A>&gt; wrote:
+</I>&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> This would reduce the space requirements on the mirrors and it would mean
+</I>&gt;&gt;&gt;<i> that Mageia is a &quot;rolling distro&quot; for most apps, making it more attractive
+</I>&gt;&gt;&gt;<i> compared to ubuntu/Fedora/opensuse and at the same time reduce the workload
+</I>&gt;&gt;&gt;<i> for packagers.
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;<i> No. No space would be saved.
+</I>&gt;&gt;<i> package foobar-1.1-2mdv2010.1 and foobar-1.1-2mdv2011.0 are _NOT_ the same
+</I>&gt;&gt;<i> They'll end in different files (different sizes&amp; checksums) b/c:
+</I>&gt;&gt;<i> - different ENVR
+</I>&gt;&gt;<i> - different build environement (build against libc+libboo+... of
+</I>&gt;&gt;<i> 2010.1&amp; 2011.1 respectively)
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i>
+</I>&gt;<i> That's not what i meant, I meant this:
+</I>&gt;<i>
+</I>&gt;<i> This is how mandriva currently does it:
+</I>&gt;<i> release/foobar-1.1-1mga2010.1
+</I>&gt;<i> updates/foobar-1.1-2mga2010.1
+</I>&gt;<i> backports/foobar-1.2-1mga2010.1
+</I>&gt;<i>
+</I>&gt;<i> This is how it would be:
+</I>&gt;<i> release/foobar-1.1-1mga2010.1
+</I>&gt;<i> updates/foobar-1.2-1mga2010.1
+</I>&gt;<i>
+</I>&gt;<i> Basically you drop the backported patch in updates (like I said
+</I>&gt;<i> earlier, this would only be for apps that don't have child dependencies
+</I>&gt;<i> and where the new release is not a major new release, just an
+</I>&gt;<i> incremental release, or at least where it's an evolution not a major
+</I>&gt;<i> rewrite).
+</I>&gt;<i>
+</I>So you are saying that the same package, with exactly the same name, is
+put into updates and backports. Are you sure there wouldn't be a hard
+link between the 2 files ? If not, it wouldn't be difficult.
+However, wouldn't it be more likely that the backport would be for an
+earlier release, with dependancies corresponding to the libraries, etc
+of the earlier release ?
+In the first case, no saving of space. In the second, additional
+libraries, etc would probably have to be installed, which could be a
+stability nightmare, as well as saving relatively little space.
+
+- Andr&#233; (andre999)
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="000956.html">[Mageia-dev] How will be the realese cycle?
+</A></li>
+ <LI>Next message: <A HREF="000943.html">[Mageia-dev] How will be the realese cycle?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#942">[ date ]</a>
+ <a href="thread.html#942">[ thread ]</a>
+ <a href="subject.html#942">[ subject ]</a>
+ <a href="author.html#942">[ 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>