all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thomas Danckaert <post@thomasdanckaert.be>
To: rekado@elephly.net
Cc: guix-devel@gnu.org
Subject: Re: hardcoded $HOME/.guix-profile in kdevelop
Date: Tue, 05 Sep 2017 08:47:18 +0200 (CEST)	[thread overview]
Message-ID: <20170905.084718.1445867273533046019.post@thomasdanckaert.be> (raw)
In-Reply-To: <87tw0iuvc7.fsf@elephly.net>

From: Ricardo Wurmus <rekado@elephly.net>
Subject: hardcoded $HOME/.guix-profile in kdevelop
Date: Mon, 04 Sep 2017 21:17:44 +0200

> I just stumbled upon commit 2f4d08ee7f897e254c6e533ad2d69c7fe4998f38
> while looking for an example of a package that uses QT_PLUGIN_PATH. 
>  I
> noticed that the above commit unconditionally adds 
> “$HOME/.guix-profile”
> to the XDG_DATA_DIRS.
>
> I think we should not hardcode the default user profile directory in
> application wrappers.  Is it really necessary to add
> “$HOME/.guix-profile” to XDG_DATA_DIRS in the wrapper?  Will the 
> package
> fail to work when it is installed to a different profile?

Hi,

some icons were missing from the interface, and adding 
<profile>/share to XDG_DATA_DIRS improved that.  But you're right 
that this is not a proper solution (I was young and naive at the time 
;-) ).  Probably it can be solved just as well by installing the 
icons in the proper directory (something like 
<out>/share/icons/hicolor ?).

I'll try to improve this.

There's a similar problem with QT_PLUGIN_PATH, though perhaps that 
will be fixed with the qt/kde install location patches people are 
currently working on.

Thomas

  reply	other threads:[~2017-09-05  6:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-04 19:17 hardcoded $HOME/.guix-profile in kdevelop Ricardo Wurmus
2017-09-05  6:47 ` Thomas Danckaert [this message]
2017-10-08 17:09 ` Thomas Danckaert

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170905.084718.1445867273533046019.post@thomasdanckaert.be \
    --to=post@thomasdanckaert.be \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.