blob: 6a6e95161fef1253c837082db1fda0ec958a3dba (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
|
<!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=%3C20110119120940.07831f8f%40pitrou.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="002238.html">
<LINK REL="Next" HREF="002229.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Python Packaging Policy</H1>
<B>Antoine Pitrou</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Python%20Packaging%20Policy&In-Reply-To=%3C20110119120940.07831f8f%40pitrou.net%3E"
TITLE="[Mageia-dev] Python Packaging Policy">solipsis at pitrou.net
</A><BR>
<I>Wed Jan 19 12:09:40 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="002238.html">[Mageia-dev] Python Packaging Policy
</A></li>
<LI>Next message: <A HREF="002229.html">[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#2239">[ date ]</a>
<a href="thread.html#2239">[ thread ]</a>
<a href="subject.html#2239">[ subject ]</a>
<a href="author.html#2239">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Wed, 19 Jan 2011 08:25:23 +0100
Michael scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>> wrote:
><i>
</I>><i> > I'm not sure about "twice the work": you don't need to track twice the
</I>><i> > software releases (except for the interpreter itself), or twice the
</I>><i> > upstream patches, etc.
</I>><i>
</I>><i> Well, if we handle this like 2 separates languages, that mean 2 separates rpms for
</I>><i> each modules. Or we should be clever when generating 1 rpm to have the modules
</I>><i> for both python 3 and python 2 generated ( Except when the developper did choose
</I>><i> to have separate tarball or code base )
</I>><i> Having one rpm that produces 2 modules also mean that we will rebuild all modules
</I>><i> for python3 and all for python2, and I know that for example Buchan will not like
</I>><i> the extranous trafic it would generate.
</I>
Well AFAIK some other distros (not Debian and Ubuntu which have a more
complicated system) have separate packages per interpreter version
(python2.4-twisted, python2.6-twisted, etc.). But you can put all
versions in a single package too. I see no hard reason against that.
Regards
Antoine.
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="002238.html">[Mageia-dev] Python Packaging Policy
</A></li>
<LI>Next message: <A HREF="002229.html">[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#2239">[ date ]</a>
<a href="thread.html#2239">[ thread ]</a>
<a href="subject.html#2239">[ subject ]</a>
<a href="author.html#2239">[ 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>
|