<!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=%3CCA%2BCX%2Bbh7E_wHde94SjXZ1X_BMuN46xBqVrxxvxePpWob3sfXng%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="018979.html">
<LINK REL="Next" HREF="018983.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] RPM groups policy</H1>
<B>Pascal Terjan</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20RPM%20groups%20policy&In-Reply-To=%3CCA%2BCX%2Bbh7E_wHde94SjXZ1X_BMuN46xBqVrxxvxePpWob3sfXng%40mail.gmail.com%3E"
TITLE="[Mageia-dev] RPM groups policy">pterjan at gmail.com
</A><BR>
<I>Thu Sep 27 11:51:54 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="018979.html">[Mageia-dev] RPM groups policy
</A></li>
<LI>Next message: <A HREF="018983.html">[Mageia-dev] RPM groups policy
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#18980">[ date ]</a>
<a href="thread.html#18980">[ thread ]</a>
<a href="subject.html#18980">[ subject ]</a>
<a href="author.html#18980">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Thu, Sep 27, 2012 at 10:48 AM, Pierre-Malo Deniélou
<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">pierre-malo.denielou at rhul.ac.uk</A>> wrote:
><i> Le 27/09/12 10:04,Colin Guthrie nous adresse ces quelques mots :
</I>>><i> Just ran into my first practical problem and would like your feedback.
</I>><i>
</I>><i> I'm guessing your email is just the first of a long list :-).
</I>><i> The new RPM group will indeed cause some head scratching for many packages.
</I>><i>
</I>>><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>><i>
</I>><i> RPM groups are for users, not necessarily technical users (technical
</I>><i> users already know which packages interest them).
</I>><i> So the main advice to find the category of a given package is:
</I>><i>
</I>><i> Where would it make sense for a user browsing through a list to find it?
</I>><i>
</I>><i> For PulseAudio, Sound/Mixer is fine.
</I>
I don't agree
If someone wants to install a mixer, pulesaudio in the list will
probably confuse him
>><i> Or perhaps PA should just go in System/Base?
</I>><i>
</I>><i> No. It only drowns it in the crowd of completely unrelated packages.
</I>
Do you expect someone to want to manually install pulseaudio after
removing it, and search it in mixers?
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="018979.html">[Mageia-dev] RPM groups policy
</A></li>
<LI>Next message: <A HREF="018983.html">[Mageia-dev] RPM groups policy
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#18980">[ date ]</a>
<a href="thread.html#18980">[ thread ]</a>
<a href="subject.html#18980">[ subject ]</a>
<a href="author.html#18980">[ 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>