all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: 35648@debbugs.gnu.org
Subject: [bug#35648] [PATCH] services: Add 'nix-service-type'.
Date: Thu, 06 Jun 2019 11:32:43 +0200	[thread overview]
Message-ID: <87v9xjnjno.fsf@gnu.org> (raw)
In-Reply-To: <877e9zqhoq.fsf@gmail.com> (Oleg Pykhalov's message of "Thu, 06 Jun 2019 10:47:01 +0300")

Hi Oleg,

Oleg Pykhalov <go.wigust@gmail.com> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
> […]
>
>>> * doc/guix.texi (Miscellaneous Services): Document this.
>
> […]
>
>>> +After @command{guix system reconfigure} you need to configure Nix
>>> for your
>>> +user, e.g.:
>>> +
>>> +@example
>>> +$ nix-channel --add https://nixos.org/channels/nixpkgs-unstable
>>> +$ nix-channel --update
>>> +$ ln -s "/nix/var/nix/profiles/per-user/$USER/profile" ~/.nix-profile
>>> +$ source /run/current-system/profile/etc/profile.d/nix.sh
>>> +$ nix-env --install hello
>>> +$ hello
>>> +@end example
>>
>> Can we instead simply add a link to upstream documentation for this?  I
>> would feel more comfortable that way.
>
> I'm not sure it will be comfortable for most of Guix users.  Upstream
> documentation doesn't mention ‘ln -s …’ step and ‘source …’ is Guix
> system relative.

What about providing just these two lines (“ln -s” and “source …”) and
adding a cross-reference to the Nix manual for more information?

If that works for you, you can push with these changes.

Thanks,
Ludo’.

  reply	other threads:[~2019-06-06  9:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09 12:29 [bug#35648] [PATCH] services: Add 'nix-service-type' Oleg Pykhalov
2019-06-01 13:26 ` Ludovic Courtès
2019-06-06  7:47   ` Oleg Pykhalov
2019-06-06  9:32     ` Ludovic Courtès [this message]
2019-06-10  6:24       ` bug#35648: " Oleg Pykhalov

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

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

  git send-email \
    --in-reply-to=87v9xjnjno.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=35648@debbugs.gnu.org \
    --cc=go.wigust@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.