On 10/25/2010 05:18 PM, Stephan Kulow wrote:
Am Montag 25 Oktober 2010 schrieb Pavol Rusnak:
In order to make our specs more cross-distro-friendly we would like to
drop %suse_update_desktop_files macro. It is currently being discussed
in this feature: https://features.opensuse.org/310621
. Ludwig suggested
managed to discuss removing the macro without adding the maintainer
to the feature?
This cannot be done via openFATE.
translation magic we do could be moved into brp-script instead
of doing it in %install phase. Is it possible? Do we have an expert in
this area who could help porting it? :-) Once this is done, we can
replace %suse_update_desktop_files with desktop-file-install if needed
(but for most cases removing the call should be enough).
For all cases where this
is done for translation only, it can most likely be
dropped. But there are many cases were this is used to change the name or
genericname (and remove outdated translations) without having to use a patch
that would break whenver translations change.
Utility desktop-file-install can do this as well (see
desktop-file-install --help-edit). If there is something missing Vincent
will add it ...
Because packagers are lazy, they would end up changing
the genericname without
removing outdated translations, providing the macro is a good way to make lazy
packagers do the right thing.
And you have a way to mark desktop files _not_ to be translated, something you
can't find out with just a brp script.
From what I see files in standard locations
/usr/share/applications/YaST2) are usually
translated, the rest is usually not. But we can work on that as well.
But that sounds like a plan:
1. move the translation magic to a brp script (possibly even one added by
prjconf, so we can remove the ugly hack that checks things based on project
This is why I wrote my origin email. Me nor Vincent could do it, that's
why we asked for help.
2. change the calls that add and remove categories in
the package to use some
Should be relatively easy.
3. make suse_update_desktop_file fail if it's a
4. leave the rest in and make them optional if building against openSUSE
I'm not sure if I understand. Why not removing macro completely?
Best Regards / S pozdravom,
Pavol RUSNAK SUSE LINUX, s.r.o
openSUSE Boosters Team Lihovarska 1060/12
PGP 0xA6917144 19000 Praha 9
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org