summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-May/015925.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2012-May/015925.html')
-rw-r--r--zarb-ml/mageia-dev/2012-May/015925.html85
1 files changed, 85 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-May/015925.html b/zarb-ml/mageia-dev/2012-May/015925.html
new file mode 100644
index 000000000..85c47dab0
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-May/015925.html
@@ -0,0 +1,85 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Pyro update
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Pyro%20update&In-Reply-To=%3C4FC4C8F8.2050002%40gmail.com%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="015924.html">
+ <LINK REL="Next" HREF="015926.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Pyro update</H1>
+ <B>Guillaume Rousse</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Pyro%20update&In-Reply-To=%3C4FC4C8F8.2050002%40gmail.com%3E"
+ TITLE="[Mageia-dev] Pyro update">guillomovitch at gmail.com
+ </A><BR>
+ <I>Tue May 29 15:02:48 CEST 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="015924.html">[Mageia-dev] Pyro update
+</A></li>
+ <LI>Next message: <A HREF="015926.html">[Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-1.mga3
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#15925">[ date ]</a>
+ <a href="thread.html#15925">[ thread ]</a>
+ <a href="subject.html#15925">[ subject ]</a>
+ <a href="author.html#15925">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le 29/05/2012 14:56, Oliver Burger a &#233;crit :
+&gt;<i> Hi there,
+</I>&gt;<i>
+</I>&gt;<i> I notice we have pyro 3.10 in the repositories. By now, according to the
+</I>&gt;<i> projects homepage at <A HREF="http://packages.python.org/Pyro4/intro.html">http://packages.python.org/Pyro4/intro.html</A> pyro
+</I>&gt;<i> 4.x (which is a reimplementation) can be considered as the main branch
+</I>&gt;<i> of the project.
+</I>&gt;<i> So what to do? Both versions of pyro are not api compatible, so just
+</I>&gt;<i> updating pyro 3.x to pyro 4.x might crush someone's applications.
+</I>That's true for all other similar librairies...
+
+&gt;<i> So should we import pyro 4.x as a versioned package and keep pyro 3.x as
+</I>&gt;<i> it is or should we rename pyro 3.x to pyro3 and import pyro 4.x as pyro?
+</I>&gt;<i> I would prefer the first way, since upstream choose to call the newer
+</I>&gt;<i> version pyro4 instead of pyro.
+</I>Without any explicit need for additional complexity, the simpler the better.
+--
+The Cavalry doesn't always come to the rescue
+ -- Murphy's Military Laws n&#176;76
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="015924.html">[Mageia-dev] Pyro update
+</A></li>
+ <LI>Next message: <A HREF="015926.html">[Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-1.mga3
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#15925">[ date ]</a>
+ <a href="thread.html#15925">[ thread ]</a>
+ <a href="subject.html#15925">[ subject ]</a>
+ <a href="author.html#15925">[ 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>