From: Lars-Dominik Braun <ldb@leibniz-psychology.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 44900@debbugs.gnu.org
Subject: [bug#44900] [PATCH] services: unattended-upgrade: Add 'search-paths' field.
Date: Mon, 30 Nov 2020 09:18:42 +0100 [thread overview]
Message-ID: <20201130081842.GB6084@zpidnp36> (raw)
In-Reply-To: <87eekdrcrw.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1399 bytes --]
Hi Ludo,
> Did you see (info "(guix) Unattended Upgrades"):
> 1. Use the trick above and add (say):
>
> (add-to-load-path (dirname (current-filename)))
>
> in your config file. Not pretty.
yes, saw it, but I wasn’t sure how to load modules from that directory. And I
agree, it’s not pretty, but probably better than option 3, because everything
is in the store.
> 2. Turn your modules into a channel. Nice because there’s no need for
> a special case, modules are automatically updated at each upgrade,
> etc., but OTOH requires more paperwork.
I feel this might be the best option and I’ll give it a try.
> I prefer being explicit here and keep ‘unattended-upgrade-configuration’
> self-contained (/etc/guix/channels.scm could be modified behind our
> back).
Okay, I can see that, but I’d like to use the same list of channels in that
service and channels.scm. Since creating an etc-service for
/etc/guix/channels.scm does not work, I was left with the other option, i.e.
using that file for unattended upgrades. Are there any other options?
Cheers,
Lars
--
Lars-Dominik Braun
Wissenschaftlicher Mitarbeiter/Research Associate
www.leibniz-psychology.org
ZPID - Leibniz-Institut für Psychologie /
ZPID - Leibniz Institute for Psychology
Universitätsring 15
D-54296 Trier - Germany
Tel.: +49–651–201-4964
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2020-11-30 8:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 8:46 [bug#44900] [PATCH] services: unattended-upgrade: Add 'search-paths' field Lars-Dominik Braun
2020-11-28 10:33 ` Ludovic Courtès
2020-11-30 8:18 ` Lars-Dominik Braun [this message]
2020-11-30 13:54 ` Ludovic Courtès
2020-12-03 8:36 ` Lars-Dominik Braun
2020-12-07 20:58 ` Ludovic Courtès
2020-12-15 8:17 ` Lars-Dominik Braun
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=20201130081842.GB6084@zpidnp36 \
--to=ldb@leibniz-psychology.org \
--cc=44900@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).