From: Ricardo Wurmus <rekado@elephly.net>
To: ng0 <ng0@n0.is>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Installation
Date: Thu, 18 Jan 2018 16:11:07 +0100 [thread overview]
Message-ID: <87bmhrgq2c.fsf@elephly.net> (raw)
In-Reply-To: <20180118120542.rymr5cwtrxogirsa@abyayala>
ng0 <ng0@n0.is> writes:
> Do we have the ability to separate features, like --enable-experimental passed
> to configure build Guix with certain features that might break your
> OS?
That would be too vague to be useful.
> Otoh
> we already presume that people setting up GuixSD today know enough about systems
> to recover from failures (which is another undocumented problem/usecase with GuixSD).
I don’t think that we do. There should not be failures that leave the
system broken. If there are then these are bugs and should be reported.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2018-01-18 15:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 12:43 Installation Gábor Boskovits
2018-01-17 14:35 ` Installation Ludovic Courtès
2018-01-17 15:47 ` Installation Ricardo Wurmus
2018-01-17 19:35 ` Installation Gábor Boskovits
2018-01-18 10:27 ` Installation Ludovic Courtès
2018-01-18 10:29 ` Installation Ludovic Courtès
2018-01-18 12:05 ` Installation ng0
2018-01-18 15:11 ` Ricardo Wurmus [this message]
2018-01-18 16:41 ` Installation myglc2
2018-01-22 4:38 ` Installation Chris Marusich
2018-01-22 8:29 ` Installation Gábor Boskovits
2018-01-18 2:29 ` Installation George myglc2 Clemmer
2018-01-18 9:29 ` Drive identifiers Danny Milosavljevic
2018-01-18 9:39 ` Danny Milosavljevic
2018-01-18 10:32 ` Ludovic Courtès
2018-01-18 11:01 ` Danny Milosavljevic
2018-01-19 14:35 ` Danny Milosavljevic
2018-01-18 20:10 ` myglc2
2018-01-19 8:27 ` Danny Milosavljevic
2018-01-19 0:43 ` myglc2
2018-01-19 7:22 ` Danny Milosavljevic
2018-01-19 16:42 ` Ricardo Wurmus
2018-01-24 14:12 ` Ludovic Courtès
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=87bmhrgq2c.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=ng0@n0.is \
/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.