Le Vendredi 14 F�vrier 2003 21:01, Warly a �crit : > Michael Scherer <[EMAIL PROTECTED]> writes: > > I have take a look at the groups classification of some package with > > rpmdrake, and I have seen there is a big lack of consistency. > > > > To give a simple example : > > > > Should wmnetload be in the GraphicalDesktop/WindowMaker group, or in the > > Monitoring group ? > > This is a wm applet who monitor the network. > > It is in GraphicalDesktop/WindowMaker > > But, another applet wmmemmon, who deal with memory used and so on, is in > > Monitoring. > > > > People searching a monitoring app would expect to found them in > > Monitoring, but, people searching cool applets for WM ( and fluxbox, btw > > ) would expect to find them in GraphicalDesktop/WindowMaker ( or in > > GraphicalDesktop / Fluxbox, who doesn't exist, even if there is more apps > > for fluxbox than for icewm ). > > > > So, they may belong to the two, but there is no way to do this in RPM, > > AFAIK. > > Yes this is a known issue. > > We have in rpmdrake a different group structure where package could appear > in several group, which is more logical.
Well, you mean that wmmemon could be in 2 or more group ? How do you do that ? In the spec file ? > Regarding you specific example, I think the very first function of the > program should be the determining criteria, and not the first limitation > (it works only in windowmaker) It works also in fluxbox, and in kde with a special taskbar, or something like that. If we put all apps of monitoring in "Monitoring", all WM applets will be moved, so almost no program will be in the GraphicalDesktop/WindowMaker group. > As a consequence, wmnetload should be in monitoring. Lenny, remember this > for the next time you rebuilt it. There is a lot of apps like this. I think I will try to do some bug report if I found the time before next week. > > And, another thing, some part of the list are unusable because some > > package take all the place. > > To give a example, webalizer and all his localization. > > The localization should be seen as subpackage of webalizer, no ? > > This applies too to vlc plugin, xmms plugin, etc . > > > > What do you think ? > > We may want to create a special i18n group where all the translation > packages are located, yes. Others ? Great idea. But what about the plugins ? It is annoying to see that that ~ 40 package are in sound only for gstreamer. Maybe, there should be a way to detect them, since they are leaf of the dependency tree, and they begin with the same prefix. Then, instead of displaying all, a new tree with the plugin will be put after gstreamer in rpmdrake. -- Micha�l Scherer
