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/2012-December/020770.html | 83 ++++++++++++++++++++++++++++ 1 file changed, 83 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-December/020770.html (limited to 'zarb-ml/mageia-dev/2012-December/020770.html') diff --git a/zarb-ml/mageia-dev/2012-December/020770.html b/zarb-ml/mageia-dev/2012-December/020770.html new file mode 100644 index 000000000..be586e13e --- /dev/null +++ b/zarb-ml/mageia-dev/2012-December/020770.html @@ -0,0 +1,83 @@ + + + + [Mageia-dev] Python packaging policy + + + + + + + + + +

[Mageia-dev] Python packaging policy

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Thu Dec 13 09:28:10 CET 2012 +

+
+ +
Le 13/12/2012 09:00, Shlomi Fish a écrit :
+>> * Also for grouping.  I'd like to add a rule that Development/Python
+>> is intended for packages
+>> which provide general development libraries for python, and if the
+>> library fits into an obvious
+>> other category (i.e. python routines for cosmology calculations) those
+>> should go into the
+>> other category.
+What is the interest ? The only usage of rpm group is in package 
+installation GUI, mostly used by end-users. They don't care of 
+development bricks, they are generally interested by ready-to-user 
+software (applications) only.
+
+Don't throw useless effort in sorting python libraries about their 
+purpose, their nature is enough.
+
+-- 
+BOFH excuse #253:
+
+We've run out of licenses
+
+ + + + + + + + + + +
+

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