unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/2] doc: Symlink daemon start-up files.
Date: Mon, 16 Jan 2017 10:49:32 +0100	[thread overview]
Message-ID: <8737gj1gib.fsf@gnu.org> (raw)
In-Reply-To: <20170115182310.GA26341@jasmine> (Leo Famulari's message of "Sun, 15 Jan 2017 13:23:10 -0500")

Leo Famulari <leo@famulari.name> skribis:

> On Fri, Nov 18, 2016 at 03:31:24PM -0500, Leo Famulari wrote:
>> On Fri, Nov 18, 2016 at 12:00:33PM +0100, Hartmut Goebel wrote:
>> > This patch ensures that always the current profile's daemon will be used.
>> > 
>> > The .service file contains the path to the guix-daemon within the store. Thus
>> > when copying the file, it will point to the very version of guix-daemon used
>> > at the time of copying – even after system upgrade or when this version has
>> > been garbage collected from the store.
>
> I think we should go back to the "old way" of instructing users to copy
> the file...
>
>> I'd argue it should point to /var/guix/profiles/per-user/root/...
>
> ... and make the service file execute this path.
>
>> >  @example
>> > -# cp ~root/.guix-profile/lib/systemd/system/guix-daemon.service \
>> > +# ln -s ~root/.guix-profile/lib/systemd/system/guix-daemon.service \
>> >          /etc/systemd/system/
>> >  # systemctl start guix-daemon && systemctl enable guix-daemon
>
> Debian Jessie (their current stable release) doesn't support symlinked
> systemd service files yet [0], and we are frequently having to explain
> to new users why this step doesn't work for them. And, we also have to
> explain that the ExecStart value that contains the absolute store path
> must be changed to point to '/var/guix/profiles...'.
>
> Doing it that way has the same effect of a symlinked file that is
> updated automatically: the daemon is always the latest in root's
> profile.
>
> It feels like we having to walk new users through this on IRC or
> help-guix every day.

I’m convinced.  :-)  Hartmut, WDYT?

Could you send a patch?

Thanks for the heads-up (and for helping out people on IRC!).
Ludo’.

  parent reply	other threads:[~2017-01-16  9:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-18 11:00 [PATCH 0/2] Hartmut Goebel
2016-11-18 11:00 ` [PATCH 1/2] doc: Symlink daemon start-up files Hartmut Goebel
2016-11-18 20:31   ` Leo Famulari
2016-11-21 16:38     ` Hartmut Goebel
2017-01-15 18:23     ` Leo Famulari
2017-01-15 19:23       ` Marius Bakke
2017-01-16  9:49       ` Ludovic Courtès [this message]
2017-03-05 20:55         ` Leo Famulari
2017-03-06  9:10           ` Hartmut Goebel
2017-03-06 10:23           ` Ludovic Courtès
2017-01-16 10:02       ` Hartmut Goebel
2016-11-18 11:00 ` [PATCH 2/2] Add system start-up files for "guix publish" Hartmut Goebel
2016-11-18 20:35   ` Leo Famulari
2016-11-21  8:52   ` Ludovic Courtès
2016-11-21 17:17     ` Hartmut Goebel
2016-11-18 20:36 ` [PATCH 0/2] Leo Famulari

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=8737gj1gib.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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).