Bug 382778

you can do a hotfix in /usr/lib/rpm/suse_update_desktop_file.sh for the desktop files you do not catch. The script knows that the file is under /usr/share/applications/YaST2 and it can add the categories automatically if not already present.

I just changed all YaST .desktop files in SVN, hoping that most of them get to autobuild due to other fixes.

Stephan, IIRC you had a script for finding changes in subversion which are not in factory, right? Perhaps we could use it in order to submit missing packages before RC1 and avoid the hotfix you suggested above (even though it does not help the few YaST modules which are not hosted in the YaST subversion repository)

I mass submitted all packs that had obviously only your change - the rest I put in ~/Export/yast2-diffs

Now it's worth - the packages do not build anymore:

ERROR: No sufficient Category definition: /var/tmp/yast2-tune-2.16.1-build//usr/share/applications/YaST2/hwinfo.desktop
ERROR: No sufficient Category definition: /var/tmp/yast2-tune-2.16.1-build//usr/share/applications/YaST2/system_settings.desktop
.

Rather worse than worth all this struggle... ;-)

> To nicely integrate with tools that are not YaST-aware

What 'tools' are we talking about btw? Obviously the YaST control center are by design the only way they are meant to be found/used.

(In reply to comment #6 from Andreas Jaeger)
> Now it's worth - the packages do not build anymore:
> 
> ERROR: No sufficient Category definition:
> /var/tmp/yast2-tune-2.16.1-build//usr/share/applications/YaST2/hwinfo.desktop
> ERROR: No sufficient Category definition:
> /var/tmp/yast2-tune-2.16.1-build//usr/share/applications/YaST2/system_settings.desktop
> .

It's not clear to me what the error means, but Stephan suggested it was because the item appeared in multiple places. I've put those categories in the desktop files on my system, and as far as I can tell, the issue would be that the items appear in System->More Programs. In this case it's just a matter of adding <Not><Category>X-SuSE-YaST</Category></Not> in the .menu file under the System->More Programs menu.

(In reply to comment #7 from Stephan Binner)
> Rather worse than worth all this struggle... ;-)
> 
> > To nicely integrate with tools that are not YaST-aware
> 
> What 'tools' are we talking about btw? Obviously the YaST control center are by
> design the only way they are meant to be found/used.

Well, all tools that might use menu files. Like the application browsers, etc. If someone uses a .menu file that we didn't patch in some way to exclude the YaST items (with the X-SuSE-YaST category), then he will see all the YaST items.  Another example is that when I build GNOME (but it's true for all other desktops, I guess) in another prefix, but still set XDG_DATA_DIRS to contain /usr/share, then I have the upstream menu structure with all the .desktop files we ship in openSUSE. Which means I get all the YaST items displayed where they shouldn't.

(also note that at least System or Settings should be added: right now, those .desktop files do not have any "main" category registered in the fd.o menu spec, and that's wrong according to the spec, which makes them invalid)

The build issue has already been fixed, marking this bug accordingly.