https://bugzilla.novell.com/show_bug.cgi?id=382778 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=382778 User jsrain@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=382778#c4 Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |coolo@novell.com --- Comment #4 from Jiri Srain 2008-05-16 09:06:02 MST --- 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) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=382778 User aj@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=382778#c6 --- Comment #6 from Andreas Jaeger 2008-05-18 00:08:17 MST --- 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 . -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=382778 User vuntz@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=382778#c8 --- Comment #8 from Vincent Untz 2008-05-18 03:28:33 MST --- (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) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.