id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc
656,where application icons and shortcuts go,daxim,,"Re r8623

This is not as easy as it looks like. I was already wracking my brain over this for a long time for [http://search.cpan.org/dist/Xacobeo/ Xacobeo], a Perl-Gtk2 app.

Spec: http://standards.freedesktop.org/menu-spec/latest/apcs02.html

[http://search.cpan.org/dist/File-BaseDir/ File::BaseDir] covers this problem partially. [http://search.cpan.org/dist/Sys-Path/ Sys::Path] (the Perl equivalent to GNU autoconf path configuration) covers this problem fully, but isn't mature yet as it asks questions to the end user that only experts can answer reasonably.

----

I will interpret the spec and resolve variables to absolute paths.

Case 1:

Admin installs Padre from vendor supplied packages. By definition, this is a system-wide installation. The typical prefix is /usr. Icons go to /usr/share/icons (regard the icon spec <http://standards.freedesktop.org/icon-theme-spec/latest/>). Desktop entries go to /usr/share/applications.

Case 2:

Admin compiles Padre from CPAN or SVN in a system-wide installation. The typical prefix is /usr/local. Icons go to /usr/local/share/icons. Desktop entries go to /usr/local/share/applications.

Case 3:

User compiles Padre from CPAN or SVN into user-specified directory. A typical prefix would be a subdirectory below $HOME or $HOME itself. Icons go to $HOME/.local/share/icons. Desktop entries go to $HOME/.local/share/applications.

----

Conclusion:

I think the path of lowest resistance to a correct (i.e. standards compliant) installation is via Sys::Path, and this module needs to be improved which is a SMOP.",enhancement,new,minor,,editor,trunk,,,