From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2011-July/006698.html | 104 +++++++++++++++++++++++++++++++ 1 file changed, 104 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-July/006698.html (limited to 'zarb-ml/mageia-dev/2011-July/006698.html') diff --git a/zarb-ml/mageia-dev/2011-July/006698.html b/zarb-ml/mageia-dev/2011-July/006698.html new file mode 100644 index 000000000..03cf8f1d1 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-July/006698.html @@ -0,0 +1,104 @@ + + + + [Mageia-dev] Python Packaging Policy + + + + + + + + + +

[Mageia-dev] Python Packaging Policy

+ Michael Scherer + misc at zarb.org +
+ Sat Jul 16 03:32:25 CEST 2011 +

+
+ +
Le mercredi 13 juillet 2011 à 09:51 +0200, philippe makowski a écrit :
+> 2011/7/13 Michael scherer <misc at zarb.org>:
+> >
+> > I would be in favor of treating python2 and python 3 as 2 differents languages.
+> > The rational is that :
+> > - we cannot garantee to have support for both
+> > -  we will likely have some module who would be updated only on
+> > python 3 sooner or later
+> > - we will need to do upgrade of package at different time, since both python2 and python3 are
+> > released at different time.
+> >
+> > So rather than a complex scheme that will confuse packagers, just consider they
+> > are separate, and use the almost same policy ( with s/python/python3/ )
+> And how do you manage package that support both P2 and P3 ?
+> (same source)
+
+Either 2 rpms with the same source, or 1 rpm that generate 2 sub rpms.
+
+I would rather use 2 separate rpms, as this seems to be easier.
+-- 
+Michael Scherer
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1