From: Sergiu Ivanov <sivanov@colimite.fr>
To: Ekaitz Zarraga <ekaitz@elenq.tech>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Defining custom services in /etc/config.scm
Date: Sun, 24 Jan 2021 20:59:17 +0100 [thread overview]
Message-ID: <87y2gicdii.fsf@colimite.fr> (raw)
In-Reply-To: <JRk3ZXh-DQLIN7gyEoDNX_g5ULD2i7aaWXeotgEG2BHthfV3Qf6t6IVk7mQVaboBcPqkBOvv7KeJbK6VTHumfTUuCbHtHt2Iog40ym-XqNQ=@elenq.tech>
Hi Ekaitz,
Thank you for your very fast answer!
Thus quoth Ekaitz Zarraga on Sun Jan 24 2021 at 20:19 (+0100):
>
> I recently made my redshift configuration using shepherd user
> services, which is what people in IRC recommended me.
>
> You can find it here:
> https://github.com/ekaitz-zarraga/dotfiles/tree/guix/shepherd/shepherd
I see, this is what I saw here as well
https://guix.gnu.org/blog/2020/gnu-shepherd-user-services/ , but
I didn't know whether I should prefer this solution over
other possibilities.
> Also, it forces me to run the shepherd as a user using my i3 config.
OK, so I note that I'll have to include shepherd in my startup scripts.
> I also wanted to configure it in my config.scm file but people
> convinced me not to do so.
Ah, interesting, good to know. Thank you for the feedback!
> I'm not sure why your case shouldn't work though.
Maybe somebody here will have the time to explain the details, but for
the time being I will go with your solution, as it has the benediction
of the IRC herd :-)
-
Sergiu
> Best,
> Ekaitz
next prev parent reply other threads:[~2021-01-24 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 19:09 Defining custom services in /etc/config.scm Sergiu Ivanov
2021-01-24 19:19 ` Ekaitz Zarraga
2021-01-24 19:59 ` Sergiu Ivanov [this message]
2021-01-24 22:25 ` Carlo Zancanaro
2021-01-25 20:50 ` Sergiu Ivanov
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=87y2gicdii.fsf@colimite.fr \
--to=sivanov@colimite.fr \
--cc=ekaitz@elenq.tech \
--cc=help-guix@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.
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).