[Mageia-dev] RPM groups policy

Thu Sep 27 11:51:54 CEST 2012

On Thu, Sep 27, 2012 at 10:48 AM, Pierre-Malo Deniélou
+<pierre-malo.denielou at rhul.ac.uk> wrote:
+> Le 27/09/12 10:04,Colin Guthrie nous adresse ces quelques mots :
+>> Just ran into my first practical problem and would like your feedback.
+>
+> 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.
+>
+>> PulseAudio packages used to just be in "Sound" group, but now I have to
+>> sub-categorise them as Sound/*. This is fine and I put everything in the
+>> Sound/Mixer category for now as this is one of the tasks PA does, mix
+>> your audio, but I get the feeling this group was more designed to
+>> represent graphical mixer UIs rather than infrastructure level stuff.
+>
+> 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 don't agree
+If someone wants to install a mixer, pulesaudio in the list will
+probably confuse him
+
+>> Or perhaps PA should just go in System/Base?
+>
+> No. It only drowns it in the crowd of completely unrelated packages.
+
+Do you expect someone to want to manually install pulseaudio after
+removing it, and search it in mixers?
+