Ticket #656 (new enhancement)

Opened 5 years ago

Last modified 4 years ago

where application icons and shortcuts go

Reported by: daxim Owned by:
Priority: minor Milestone:
Component: editor Version: trunk
Keywords: Cc:

Description

Re r8623

This is not as easy as it looks like. I was already wracking my brain over this for a long time for Xacobeo, a Perl-Gtk2 app.

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

File::BaseDir covers this problem partially. 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.

Change History

comment:1 Changed 4 years ago by dolmen

And none of those icons must be installed on Win32 (except if they are used by Padre at runtime): the icon used for shortcut must be the one embeded in padre.exe.

Note: See TracTickets for help on using tickets.