summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-December/020775.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2012-December/020775.html')
-rw-r--r--zarb-ml/mageia-dev/2012-December/020775.html117
1 files changed, 117 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-December/020775.html b/zarb-ml/mageia-dev/2012-December/020775.html
new file mode 100644
index 000000000..e853f9623
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-December/020775.html
@@ -0,0 +1,117 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Python packaging policy
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Python%20packaging%20policy&In-Reply-To=%3C50CA0833.1070704%40zarb.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="020774.html">
+ <LINK REL="Next" HREF="020776.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Python packaging policy</H1>
+ <B>Claire REVILLET</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Python%20packaging%20policy&In-Reply-To=%3C50CA0833.1070704%40zarb.org%3E"
+ TITLE="[Mageia-dev] Python packaging policy">grenoya at zarb.org
+ </A><BR>
+ <I>Thu Dec 13 17:54:11 CET 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="020774.html">[Mageia-dev] Python packaging policy
+</A></li>
+ <LI>Next message: <A HREF="020776.html">[Mageia-dev] Python packaging policy
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#20775">[ date ]</a>
+ <a href="thread.html#20775">[ thread ]</a>
+ <a href="subject.html#20775">[ subject ]</a>
+ <a href="author.html#20775">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le 13/12/2012 15:43, Guillaume Rousse a &#233;crit :
+&gt;<i> Le 13/12/2012 15:24, Claire REVILLET a &#233;crit :
+</I>&gt;&gt;<i> Hi,
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Le 13/12/2012 09:00, Shlomi Fish a &#233;crit :
+</I>&gt;&gt;&gt;<i> Hi Joseph,
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> On Thu, 13 Dec 2012 14:53:04 +0800
+</I>&gt;&gt;&gt;<i> Joseph Wang&lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">joequant at gmail.com</A>&gt; wrote:
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;<i> [...]
+</I>&gt;&gt;&gt;&gt;<i> * I'd like to add a rule (which is followed by current packages) that
+</I>&gt;&gt;&gt;&gt;<i> the prefix &quot;py&quot; should
+</I>&gt;&gt;&gt;&gt;<i> generally be removed from a package name. For example pyopencl
+</I>&gt;&gt;&gt;&gt;<i> should be
+</I>&gt;&gt;&gt;&gt;<i> called python-opencl. This is the current convention for packages in
+</I>&gt;&gt;&gt;&gt;<i> mageia.
+</I>&gt;&gt;&gt;<i> I'm OK with it either way.
+</I>&gt;&gt;<i> I disagree on that point: software and libraries names are choose by the
+</I>&gt;&gt;<i> developers.
+</I>&gt;&gt;<i> Who are we to change them ?
+</I>&gt;<i> A free software distribution, whose part of the added value is overall
+</I>&gt;<i> consistency. Which is out of scope of individual software authors by
+</I>&gt;<i> definition.
+</I>&gt;<i>
+</I>&gt;<i> And the current issue is just about the *package* name, not exactly
+</I>&gt;<i> the software name. Remember when 'thunderbird' was distributed as
+</I>&gt;<i> 'mozilla-thunderbird' ?
+</I>&gt;<i>
+</I>&gt;<i> And just to compare it with other similar practices:
+</I>&gt;<i> - we already normalize perl version numbers, for sorting purpose
+</I>&gt;<i> - we already force lowercase package naming
+</I>&gt;<i> - we already modify software setup, to achieve FHS compliance
+</I>&gt;<i> - we already modify package behaviour, to prevent automatic upgrade,
+</I>&gt;<i> for instance
+</I>&gt;<i>
+</I>&gt;<i> The two latest ones seems far most invasive IMHO than just shipping
+</I>&gt;<i> pycups in a package called 'python-cups' rather than 'python-pycups'.
+</I>&gt;<i>
+</I>I understand your point, but i fear collisions between package names:
+(this is not a true example, i can't find one just now)
+Imagine it exists &quot;toto&quot; and &quot;pytoto&quot; in the Python Package Index. It
+can happen just because some people don't feel the need to add &quot;py&quot; in
+the module name as it's already written in python and it's in the Python
+package index... which seems sensible.
+Imagine &quot;pytoto&quot; is imported first with &quot;python-toto&quot; name for the package.
+How should i name the package for &quot;toto&quot; ?
+
+We can rename the first one into &quot;python-pytoto&quot; and import the second
+with &quot;python-toto&quot;, but we have to take care of the packages with BR or
+R on the first one. And it will brake the new policy rule.
+
+my 2 cents.
+Claire
+
+</PRE>
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="020774.html">[Mageia-dev] Python packaging policy
+</A></li>
+ <LI>Next message: <A HREF="020776.html">[Mageia-dev] Python packaging policy
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#20775">[ date ]</a>
+ <a href="thread.html#20775">[ thread ]</a>
+ <a href="subject.html#20775">[ subject ]</a>
+ <a href="author.html#20775">[ 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>