<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] RPM groups policy
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20RPM%20groups%20policy&In-Reply-To=%3C506420E6.3000406%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="018977.html">
<LINK REL="Next" HREF="018980.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] RPM groups policy</H1>
<B>Pierre-Malo Deniélou</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20RPM%20groups%20policy&In-Reply-To=%3C506420E6.3000406%40rhul.ac.uk%3E"
TITLE="[Mageia-dev] RPM groups policy">pierre-malo.denielou at rhul.ac.uk
</A><BR>
<I>Thu Sep 27 11:48:22 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="018977.html">[Mageia-dev] RPM groups policy
</A></li>
<LI>Next message: <A HREF="018980.html">[Mageia-dev] RPM groups policy
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#18979">[ date ]</a>
<a href="thread.html#18979">[ thread ]</a>
<a href="subject.html#18979">[ subject ]</a>
<a href="author.html#18979">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le 27/09/12 10:04,Colin Guthrie nous adresse ces quelques mots :
><i> Just ran into my first practical problem and would like your feedback.
</I>
I'm guessing your email is just the first of a long list :-).
The new RPM group will indeed cause some head scratching for many packages.
><i> PulseAudio packages used to just be in "Sound" group, but now I have to
</I>><i> sub-categorise them as Sound/*. This is fine and I put everything in the
</I>><i> Sound/Mixer category for now as this is one of the tasks PA does, mix
</I>><i> your audio, but I get the feeling this group was more designed to
</I>><i> represent graphical mixer UIs rather than infrastructure level stuff.
</I>
RPM groups are for users, not necessarily technical users (technical
users already know which packages interest them).
So the main advice to find the category of a given package is:
Where would it make sense for a user browsing through a list to find it?
For PulseAudio, Sound/Mixer is fine.
><i> Should there be a group that represents this better? e.g.
</I>><i>
</I>><i> Sound/Plumbing
</I>><i> System/Sound
</I>><i> Plumbing/Sound
</I>
Or Sound/PulseAudio ... :-P
That's the Suse approach, but it does not work. It only multiplies the
groups, with 3 or 4 subdivision depths (Amusements/Games/Strategy/Turn
Based ...), with some groups only having a handful of packages. Many of
the subdivisions make sense from a packaging point of view, but from a
user point of view it makes browsing too precise. I personally think
that groups are meant for the exploration by people who don't know what
they are looking for.
><i> Or perhaps PA should just go in System/Base?
</I>
No. It only drowns it in the crowd of completely unrelated packages.
><i> (I use the term Plumbing as this is quite common these days as an off
</I>><i> shoot perhaps from the Linux Plumbers Conference where the various
</I>><i> infrastructural bits of linux are discussed).
</I>><i>
</I>><i> Thoughts?
</I>
No RPM group classification is perfect. There will always be a package
that does not fit the classification. So we should stick to the "best
guess" strategy for now.
The new RPM group policy is not completely fixed, but I propose that
everyone tries to stick with it until Beta 1, at which point we can
review it and amend the most obvious problems.
Cheers,
--
Malo
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="018977.html">[Mageia-dev] RPM groups policy
</A></li>
<LI>Next message: <A HREF="018980.html">[Mageia-dev] RPM groups policy
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#18979">[ date ]</a>
<a href="thread.html#18979">[ thread ]</a>
<a href="subject.html#18979">[ subject ]</a>
<a href="author.html#18979">[ 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>