blob: be586e13e3932d379eb361f09b2446eab890630f (
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
|
<!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=%3C50C9919A.5000305%40gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="020769.html">
<LINK REL="Next" HREF="020772.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Python packaging policy</H1>
<B>Guillaume Rousse</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Python%20packaging%20policy&In-Reply-To=%3C50C9919A.5000305%40gmail.com%3E"
TITLE="[Mageia-dev] Python packaging policy">guillomovitch at gmail.com
</A><BR>
<I>Thu Dec 13 09:28:10 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="020769.html">[Mageia-dev] Python packaging policy
</A></li>
<LI>Next message: <A HREF="020772.html">[Mageia-dev] Python packaging policy
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#20770">[ date ]</a>
<a href="thread.html#20770">[ thread ]</a>
<a href="subject.html#20770">[ subject ]</a>
<a href="author.html#20770">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le 13/12/2012 09:00, Shlomi Fish a écrit :
>><i> * Also for grouping. I'd like to add a rule that Development/Python
</I>>><i> is intended for packages
</I>>><i> which provide general development libraries for python, and if the
</I>>><i> library fits into an obvious
</I>>><i> other category (i.e. python routines for cosmology calculations) those
</I>>><i> should go into the
</I>>><i> other category.
</I>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
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="020769.html">[Mageia-dev] Python packaging policy
</A></li>
<LI>Next message: <A HREF="020772.html">[Mageia-dev] Python packaging policy
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#20770">[ date ]</a>
<a href="thread.html#20770">[ thread ]</a>
<a href="subject.html#20770">[ subject ]</a>
<a href="author.html#20770">[ 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>
|
