unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Fis Trivial <ybbs.daans@hotmail.com>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Install doc (binary installation)
Date: Thu, 28 Dec 2017 10:59:39 +0000	[thread overview]
Message-ID: <DM5PR16MB00590F1FE19B8654BD59A3A092040@DM5PR16MB0059.namprd16.prod.outlook.com> (raw)
In-Reply-To: <20171227171609.GA11103@thebird.nl>


On 12/28/2017 01:16 AM, Pjotr Prins wrote:
> I just went through
>
>   https://www.gnu.org/software/guix/manual/html_node/Binary-Installation.html
>
> And it works well enough.
>
> Two minor niggles:
>
> 1. Can we inline section 4 on creating users and build group? I think
>    people easily miss this step now, creating problems a bit later.
>
> 2. Add 'guix pull' step. I am no fan of the latter, but doing a 'guix
>    package -i guix' installs an older version which we may want to
>    avoid.
>
> Otherwise it is nice as ever. HNY.
>
> Pj.
>
I am afraid that the installation steps described in the doc is still far from complete.
There are many per-system configuration that might affect the installation of Guix.
For examples:

    Default sudo file on Fedora preserves the USERNAME env which will lead Guix to
link login user's profile even if Guix running as root (via sudo).
    Guix is not welcomed by SeLinux, on enabled system, you need to configure or
disable SeLinux in order to run the guix-daemon properly. Configuring SeLinux
takes patient while disabling it takes guts.

I have written a script for basic installation but didn't share it with anyone due to
the fact that things can vary in a quite dramatic way and I simply don't have enough
knowledge to cover them.

      reply	other threads:[~2017-12-28 10:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-27 17:16 Install doc (binary installation) Pjotr Prins
2017-12-28 10:59 ` Fis Trivial [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

  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=DM5PR16MB00590F1FE19B8654BD59A3A092040@DM5PR16MB0059.namprd16.prod.outlook.com \
    --to=ybbs.daans@hotmail.com \
    --cc=guix-devel@gnu.org \
    --cc=pjotr.public12@thebird.nl \
    /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).