Do we need a full path? I think desktop files know to search $PATH
for executables.
On Tue, Aug 4, 2009 at 1:14 PM, Paweł Hajdan Jr.phajdan...@chromium.org wrote:
There is one problem with creating desktop shortcuts on Linux: getting
correct path to the launcher script.
Gears find Firefox
E.g. this successfully starts xeyes when you click on it.
[Desktop Entry]
Version=1.0
Encoding=UTF-8
Name=test.txt
Type=Application
Exec=xeyes
Name[en_US]=test.txt
On Tue, Aug 4, 2009 at 1:17 PM, Evan Martine...@chromium.org wrote:
Do we need a full path? I think desktop files know to search
Yes, but even then we need to know how the launcher is named. Hardcoding
google-chrome is not good for chromium builds (and we are going to have
Chromium packaged for Gentoo). Having it chromium for Chromium is also not
good, because of the conflict with Chromium (the game).
On Tue, Aug 4, 2009
There should also already be a desktop file for Chrome/Chromium on the
system; you might consider using it as a template in order to create
the desktop shortcut. You can find it by searching a set of
directories given by the environment variables $XDG_DATA_HOME and
$XDG_DATA_DIRS, the former
Ah, yes. I actually sorta hacked this for the manpage. See the
manpage rule in chrome/chrome.gyp.
Perhaps that could be generalized at a higher level so that the
filename variable (which is really the binary name) is available to
you as well. Maybe via a -D flag? See also the discussion on
Thanks. Looks like a good solution.
How about a case when there is no desktop file? I don't have better idea
than displaying an error message.
On Tue, Aug 4, 2009 at 13:28, Mike Mammarella m...@chromium.org wrote:
There should also already be a desktop file for Chrome/Chromium on the
system;
Yeah, there's not much you can do in that case. For the default
browser setting, when there's no desktop file it just claims that it's
the default browser to avoid bothering you about it every time.
Fortunately that case should only occur with people running unpackaged
versions and not using that
On Tue, Aug 4, 2009 at 1:22 PM, Paweł Hajdan Jr.phajdan...@chromium.org wrote:
Yes, but even then we need to know how the launcher is named. Hardcoding
google-chrome is not good for chromium builds (and we are going to have
Chromium packaged for Gentoo). Having it chromium for Chromium is also
