From: "Hamzeh Nasajpour" <h.nasajpour@pantherx.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 37725@debbugs.gnu.org
Subject: [bug#37725] [PATCH] gnu: lxqt-config: Add libkscreen as propagated-inputs.
Date: Mon, 14 Oct 2019 09:20:26 +0330 [thread overview]
Message-ID: <4877c727-7890-41ca-a817-ca8346011c38@www.fastmail.com> (raw)
In-Reply-To: <87o8yk7103.fsf@gnu.org>
Hi,
The problem is crashing the `lxqt-config-monitor` when I want to run it(`segmentation fault`). I installed the `libkscreen` and the problem was resolved. So I change the `lxqt-config` package definition and remove the `libkscreen` from `inputs` to `propagated-inputs`, install it and everything was ok.
Regards,
Hamzeh.
On Mon, Oct 14, 2019, at 1:37 AM, Ludovic Courtès wrote:
> Hi,
>
> "Hamzeh Nasajpour" <h.nasajpour@pantherx.org> skribis:
>
> > * gnu/packages/lxqt.scm (lxqt-config): Remove libkscreen from native-inputs to propagated-inputs for running the lxqt-config-monitor.
>
> In general, when adding a propagated input, could you add a comment in
> the code itself explaining why it’s this way?
>
> In this particular case, is the ‘lxqt-config-monitor’ command part of
> libkscreen? Could we avoid propagation somehow?
>
> Thanks,
> Ludo’.
>
next prev parent reply other threads:[~2019-10-14 5:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-13 4:23 [bug#37725] [PATCH] gnu: lxqt-config: Add libkscreen as propagated-inputs Hamzeh Nasajpour
2019-10-13 22:07 ` Ludovic Courtès
2019-10-14 5:50 ` Hamzeh Nasajpour [this message]
2019-10-14 20:21 ` Ludovic Courtès
2020-04-02 19:17 ` Hamzeh Nasajpour
2020-04-27 16:39 ` Efraim Flashner
2019-10-16 11:18 ` Reza Alizadeh Majd
2019-10-18 9:54 ` Ludovic Courtès
2019-10-18 16:44 ` Reza Alizadeh Majd
2020-04-22 15:50 ` Ludovic Courtès
2020-09-16 8:40 ` Hamzeh Nasajpour via web
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=4877c727-7890-41ca-a817-ca8346011c38@www.fastmail.com \
--to=h.nasajpour@pantherx.org \
--cc=37725@debbugs.gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.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).