From: Oleg Pykhalov <go.wigust@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 35648-done@debbugs.gnu.org
Subject: bug#35648: [PATCH] services: Add 'nix-service-type'.
Date: Mon, 10 Jun 2019 09:24:06 +0300 [thread overview]
Message-ID: <87sgsiarg9.fsf@gmail.com> (raw)
In-Reply-To: <87v9xjnjno.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 06 Jun 2019 11:32:43 +0200")
[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
[…]
>>>> +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.
OK, pushed as 47b9614b3110307093382363c0ba70d31f32ef59 to master.
Thanks,
Oleg.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2019-06-10 6:25 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
2019-06-10 6:24 ` Oleg Pykhalov [this message]
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=87sgsiarg9.fsf@gmail.com \
--to=go.wigust@gmail.com \
--cc=35648-done@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 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.