Publican Issues for RNs

[Jeff Fearn]

On 03/13/2009 10:58 AM, David Nalley wrote:
>
>> From that section: (and emphasis is in the packaging guidelines, I
> didn't add it):
> It is not simply enough to just include the .desktop file in the
> package, one MUST run desktop-file-install OR desktop-file-validate in
> %install (and have BuildRequires: desktop-file-utils), to help ensure
> .desktop file safety and spec-compliance. desktop-file-install MUST be
> used if the package does not install the file or there are changes
> desired to the .desktop file (such as add/removing categories, etc).
>

These are real bugs, if you open a separate BZ I will fix these issues 
in a timely manner.

The complaint in the original bug is that the .desktop file is embedded 
in the spec file and is created when the binary rpms are built in Koji. 
They want the desktop file created when the srpm is created. Doing so 
breaks the desktop file for other rpm based distros, like Suse, who use 
different documentation paths. Embedding the desktop file in the spec 
means that at compile time we can source docdir from the build system 
creating proper desktop files for the system it is being built on.

While I can understand that distros may not care if other distros break 
or have to do extra work to get a proper desktop file, publican wants to 
work on these other distros, so the extra work will have to be done by 
the distro requesting the breaking change.

Cheers, Jeff.