summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-June/006048.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/006048.html')
-rw-r--r--zarb-ml/mageia-dev/2011-June/006048.html121
1 files changed, 121 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/006048.html b/zarb-ml/mageia-dev/2011-June/006048.html
new file mode 100644
index 000000000..04568ebb1
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-June/006048.html
@@ -0,0 +1,121 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Update of backport, policy proposal
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Update%20of%20backport%2C%20policy%20proposal&In-Reply-To=%3C201106261851.42601.anaselli%40linux.it%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="006043.html">
+ <LINK REL="Next" HREF="006076.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Update of backport, policy proposal</H1>
+ <B>Angelo Naselli</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Update%20of%20backport%2C%20policy%20proposal&In-Reply-To=%3C201106261851.42601.anaselli%40linux.it%3E"
+ TITLE="[Mageia-dev] Update of backport, policy proposal">anaselli at linux.it
+ </A><BR>
+ <I>Sun Jun 26 18:51:39 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="006043.html">[Mageia-dev] Update of backport, policy proposal
+</A></li>
+ <LI>Next message: <A HREF="006076.html">[Mageia-dev] Update of backport, policy proposal
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#6048">[ date ]</a>
+ <a href="thread.html#6048">[ thread ]</a>
+ <a href="subject.html#6048">[ subject ]</a>
+ <a href="author.html#6048">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>&gt;<i> Well, in principle this is correct, not in this case as I have
+</I>&gt;<i> explained as a very common example. You can decide whatever you want,
+</I>&gt;<i> if a user wants a certain package and his friend will pack it for him
+</I>&gt;<i> and puts it up on a server, publishing the existence - then you will
+</I>&gt;<i> see what happens. You know by experience how popular such 3rd-party
+</I>&gt;<i> repos can become (see MIB, MUD), just because somebody had a different
+</I>&gt;<i> view than the official view.
+</I>&gt;<i> In short: no matter what is more important or not, you have to find a
+</I>&gt;<i> compromise between the (understandable) search for optimal workflow,
+</I>&gt;<i> security on one side and the real world of the users on the other. I
+</I>&gt;<i> think, the key here is non-technical communication of the
+</I>&gt;<i> circumstances, like &quot;why we can't have foo 1.2 as backport from
+</I>&gt;<i> Cauldron to Mageia 1&quot;.
+</I>Well I'm one who backports what he needs, doesn't mean all, just what needs.
+I always enable backports, and i know often how to go on if a backport was
+broken. That's not a point though.
+I can't see why people that want last release of all must trust 3rd-party
+repos and do not mageia(or mandriva) backport one... it's really hard to me.
+
+I think we can, as said by someone, release all as updates, but we can also
+consider to have a tested and reliable backport repository (call as you wish
+maybe &quot;next&quot; or &quot;after&quot; :) ) but the real concept to me is that we should
+have the availability to get new sw or version of a sw in a repository that
+could be different than updates, *could* because case by case we could
+consider to add them in updates and in any case that should be reliable,
+no breakages, no regressions.
+
+We talked about patches, and sometime we could patch sw, but sometime
+it's hard, and updates with an upgrade of such a sw should be the best
+thing to do.
+
+Cheers,
+--
+ Angelo
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 198 bytes
+Desc: This is a digitally signed message part.
+URL: &lt;/pipermail/mageia-dev/attachments/20110626/2742f31c/attachment.asc&gt;
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="006043.html">[Mageia-dev] Update of backport, policy proposal
+</A></li>
+ <LI>Next message: <A HREF="006076.html">[Mageia-dev] Update of backport, policy proposal
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#6048">[ date ]</a>
+ <a href="thread.html#6048">[ thread ]</a>
+ <a href="subject.html#6048">[ subject ]</a>
+ <a href="author.html#6048">[ 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>