summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-September/018616.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2012-September/018616.html')
-rw-r--r--zarb-ml/mageia-dev/2012-September/018616.html121
1 files changed, 121 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-September/018616.html b/zarb-ml/mageia-dev/2012-September/018616.html
new file mode 100644
index 000000000..557ef4145
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-September/018616.html
@@ -0,0 +1,121 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Update of the rpm group policy
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Update%20of%20the%20rpm%20group%20policy&In-Reply-To=%3C504E5A64.2080806%40rhul.ac.uk%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="018699.html">
+ <LINK REL="Next" HREF="018748.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Update of the rpm group policy</H1>
+ <B>Pierre-Malo Deni&#233;lou</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Update%20of%20the%20rpm%20group%20policy&In-Reply-To=%3C504E5A64.2080806%40rhul.ac.uk%3E"
+ TITLE="[Mageia-dev] Update of the rpm group policy">pierre-malo.denielou at rhul.ac.uk
+ </A><BR>
+ <I>Mon Sep 10 23:23:48 CEST 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="018699.html">[Mageia-dev] Update of the rpm group policy
+</A></li>
+ <LI>Next message: <A HREF="018748.html">[Mageia-dev] Update of the rpm group policy
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#18616">[ date ]</a>
+ <a href="thread.html#18616">[ thread ]</a>
+ <a href="subject.html#18616">[ subject ]</a>
+ <a href="author.html#18616">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le 10/09/12 11:53,Barry Jackson nous adresse ces quelques mots :
+&gt;<i> On 08/09/12 19:07, Pierre-Malo Deni&#233;lou wrote:
+</I>&gt;<i>
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Any other suggestions for the groups?
+</I>&gt;&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i> gnuradio is development software for &quot;software enabled radio&quot;, so
+</I>&gt;<i> Communications/Development
+</I>&gt;<i>
+</I>&gt;<i> Amateur Radio is needed as a group for packages like grig and xlog,
+</I>&gt;<i> so maybe:
+</I>&gt;<i> Communications/Amateur Radio
+</I>&gt;<i>
+</I>&gt;<i> cutecw is a Morse Code trainer aimed at radio amateurs so:
+</I>&gt;<i> Communications/Amateur Radio/Education
+</I>&gt;<i>
+</I>&gt;<i> zoneminder is currently in Video which is rather cluttered.
+</I>&gt;<i> I think Video needs sub-groups like:-
+</I>&gt;<i> Video/Players
+</I>&gt;<i> Video/Editors
+</I>&gt;<i> Video/Security
+</I>&gt;<i> Video/Format converters
+</I>&gt;<i> Video/Plug-ins
+</I>
+Doing changes like this would mean to go towards a more Suse-like
+system, with hundreds of rpm package groups that each contain a few
+packages.
+That is one option, but it requires to updates the specs of several
+thousands packages.
+
+My proposal is more limited:
+- let's split the groups that have obviously too many different packages
+(Development/Other is an example) to the point that it is unpractical to
+browse.
+- let's create a handful of categories that (1) make sense for packages
+that are currently in unrelated groups (motivated by security software
+for example); and (2) complete existing subdivisions (so as not to have
+to change the spec of too many packages)
+
+Only creating a few groups also lessens the burden for icons and
+translations.
+
+With that in mind, I'm not sure this is a good idea to get so
+fine-grained categories in Video, or communications, especially if it's
+just for one package.
+Maybe if we create a Security group, things like zoneminder can go
+there. For amateur radio, in communication it's fine IMHO.
+Communications has 138 packages, so it's reasonable.
+
+&gt;<i> Also, why has gpg got it's own top level 'Public Keys' group which
+</I>&gt;<i> clutters rpmdrake - surely this should be somewhere down the System/..
+</I>&gt;<i> hierarchy?
+</I>
+The public key thing does not correspond to a rpm group. It's a rpmdrake
+GUI choice of how to display keys AFAICT. Feel free to suggest to tv
+another choice for the display :-).
+
+Cheers,
+--
+Malo
+</PRE>
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="018699.html">[Mageia-dev] Update of the rpm group policy
+</A></li>
+ <LI>Next message: <A HREF="018748.html">[Mageia-dev] Update of the rpm group policy
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#18616">[ date ]</a>
+ <a href="thread.html#18616">[ thread ]</a>
+ <a href="subject.html#18616">[ subject ]</a>
+ <a href="author.html#18616">[ 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>