unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: L  p R n  d n    <guix@lprndn.info>
To: Reza Alizadeh Majd <r.majd@pantherx.org>
Cc: help-guix@gnu.org
Subject: Re: Problem on LXQt service definition
Date: Wed, 15 May 2019 15:53:17 +0200	[thread overview]
Message-ID: <87zhnnbz8y.fsf@lprndn.info> (raw)
In-Reply-To: <b58232bd-ca91-46b3-899d-ec7fb39e70c8@www.fastmail.com> (Reza Alizadeh Majd's message of "Wed, 15 May 2019 14:17:49 +0430")

Hello

"Reza Alizadeh Majd" <r.majd@pantherx.org> writes:

> Hi, 
>
> Thanks for your response. 
>
> based on my researches about using LXQt as a service on guix (like other desktop
> services previously defined), I found following comment on LXQt's Github:
> https://github.com/lxqt/lxqt/issues/1521#issuecomment-405097453
>
> It seems that I need to customize `$XDG_CONFIG_DIRS` in order to be able to load
> session files from `prefix/etc/share` instead of `prefix/etc/xdg` but I couldn't
> find a proper way to do this, and hoped that defining a shepherd service with
> modified environment variables in it's start script could help.
>
> do we have any reference about modification of environment variables during service start? 
>
> Thanks,
> Reza
>

Sorry if I'm beside the point, just want to be sure, did you try to
get lxqt by just adding it to your system profile?
I tried lxqt once and I don't remember experiencing the problems
described in your link.

Also, from what I've seen in gnu/services/desktop.scm, desktop services are
often just polkit or dbus extensions, if some lxqt packages need a
special environment variable, another solution is to modify the package
definition with a `wrap-program` phase or something. This way, the
problem should be solved even if the user doesn't use the service.



Thanks,

L  p R n  d n

      reply	other threads:[~2019-05-15 11:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-13 18:33 Problem on LXQt service definition Reza Alizadeh Majd
2019-05-15  3:28 ` Meiyo Peng
2019-05-15  9:47   ` Reza Alizadeh Majd
2019-05-15 13:53     ` L p R n d n [this message]

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87zhnnbz8y.fsf@lprndn.info \
    --to=guix@lprndn.info \
    --cc=help-guix@gnu.org \
    --cc=r.majd@pantherx.org \
    /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.
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).