From: Glenn Morris <rgm@gnu.org>
To: markskilbeck@gmail.com
Cc: 12932@debbugs.gnu.org
Subject: bug#12932: 24.2; Installing GNOME .desktop file to incorrect location
Date: Mon, 19 Nov 2012 14:06:23 -0500 [thread overview]
Message-ID: <6awqxhpg40.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <753905cyek.fsf@fencepost.gnu.org> (Glenn Morris's message of "Mon, 19 Nov 2012 12:09:39 -0500")
I guess we could add an explicit configure option for where the desktop
file will be installed ($desktopdir in current Makefile), and leave the
default as it is now. I doubt the option will see much use though.
But the freedesktop spec does mention (obliquely) /usr/local:
http://specifications.freedesktop.org/menu-spec/menu-spec-latest.html
Install Locations
If an application is intended to be installed by root on a system
wide basis then /usr/share is recommended to be used as value for
datadir and /etc/xdg is recommended to be used as value for
sysconfdir. In case the /usr/share hierarchy is not writable it is
recommended to use /usr/local/share as value for datadir instead.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
So, again, it seems like a Gnome bug to me if it doesn't check in
/usr/local as well as /usr (I didn't check whether or not it actually does).
See also
http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html
If $XDG_DATA_DIRS is either not set or empty, a value equal to
/usr/local/share/:/usr/share/ should be used.
Maybe your XDG_DATA_DIRS is set wrongly?
Of course, this doesn't help people who install with --prefix != /usr/local
next prev parent reply other threads:[~2012-11-19 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 8:49 bug#12932: 24.2; Installing GNOME .desktop file to incorrect location markskilbeck
2012-11-19 17:09 ` Glenn Morris
2012-11-19 19:06 ` Glenn Morris [this message]
2012-11-19 19:49 ` Stefan Monnier
2012-11-19 20:08 ` Mark Skilbeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6awqxhpg40.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=12932@debbugs.gnu.org \
--cc=markskilbeck@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).