blob: fad5cecba520cb69d70c46f21b1cf11d2f7a23b3 (
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
81
82
83
84
85
86
87
|
<!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=%3CCAPoeEY_2%3D_iacDkLZCqAJUf0rcQg_0EoFVfuyO9wCO5kkc33Dw%40mail.gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="020762.html">
<LINK REL="Next" HREF="020769.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Python packaging policy</H1>
<B>Joseph Wang</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Python%20packaging%20policy&In-Reply-To=%3CCAPoeEY_2%3D_iacDkLZCqAJUf0rcQg_0EoFVfuyO9wCO5kkc33Dw%40mail.gmail.com%3E"
TITLE="[Mageia-dev] Python packaging policy">joequant at gmail.com
</A><BR>
<I>Thu Dec 13 07:53:04 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="020762.html">[Mageia-dev] [changelog] [RPM] cauldron core/release gtk-engines2-2.20.2-3.mga3
</A></li>
<LI>Next message: <A HREF="020769.html">[Mageia-dev] Python packaging policy
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#20768">[ date ]</a>
<a href="thread.html#20768">[ thread ]</a>
<a href="subject.html#20768">[ subject ]</a>
<a href="author.html#20768">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Looking over this page:
<A HREF="https://wiki.mageia.org/en/Python_policy">https://wiki.mageia.org/en/Python_policy</A>
* python-pyp2rpm is undergoing review right now. Once it's in
cauldron, I'd like to
point to that package as something that packagers you should use to
get a first draft
of a spec file, I've been working with the Fedora people so that it
will do both fedora
and mageia naming conventions.
* I'd like to add a rule (which is followed by current packages) that
the prefix "py" should
generally be removed from a package name. For example pyopencl should be called
python-opencl. This is the current convention for packages in mageia.
* 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.
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="020762.html">[Mageia-dev] [changelog] [RPM] cauldron core/release gtk-engines2-2.20.2-3.mga3
</A></li>
<LI>Next message: <A HREF="020769.html">[Mageia-dev] Python packaging policy
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#20768">[ date ]</a>
<a href="thread.html#20768">[ thread ]</a>
<a href="subject.html#20768">[ subject ]</a>
<a href="author.html#20768">[ 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>
|
