From: iyzsong@member.fsf.org (宋文武)
To: dian_cecht@zoho.com
Cc: help-guix@gnu.org
Subject: Re: Some questions regarding GuixSD
Date: Sat, 01 Oct 2016 09:50:11 +0800 [thread overview]
Message-ID: <87vaxckfcc.fsf@member.fsf.org> (raw)
In-Reply-To: <20160930194615.GA17165@khaalida> (dian cecht's message of "Fri, 30 Sep 2016 12:46:15 -0700")
dian_cecht@zoho.com writes:
> On Fri, Sep 30, 2016 at 10:18:40AM +0200, Ludovic Courtès wrote:
>> > 2) Are multiple versions of a package in the tree at any given time?
>>
>> You can have multiple profiles, each containing a different version of a
>> given package, for example.
>>
>> The source tree of Guix itself usually only contains the latest version
>> of each package. There are exceptions for packages where it makes sense
>> to keep several stable series in parallel: GCC, Python, Guile, etc.
>
> I don't know where Guix/GuixSD is in regards to the plans for it, and I havn't
> had a chance to glance at the ROADMAP you mentioned later in this email, but I
> can say from personal experience that maintaining one and only one version of a
> package in a tree is a Really Bad Idea. When I used Arch they had (and may still
> have, I have no clue what has happened with that distro since) a policy to only
> maintain one version of any package at any given time in the distro. This is a
> huge PITA and sometimes can make a system unusable if a package breaks. I
> distinctly recall having one package I relied on breaking when I used Arch and
> having to wait a few days for them to release a new version.
On GuixSD, you can rollback the whole system safely and easily (by
choosing a grub menu item at boot). And the CI service (hydra) is
building (each package if any of its inputs changed) and testing (system
with services in qemu) the whole distribution.
While in Guix it's easier than Debian or ArchLinux to have multiple
versions of the same packages, it's reasonble only do it when needed :-)
>
>>
>> > 3) Is there any way to install GuixSD from something other than the LiveUSB
>> > image on the site?
>>
>> You can install Guix on top of your GNU/Linux system and run:
>>
>> guix system init config.scm /
>>
>> Be careful: this is a one-way change!
>
> So as long as Guix is installed correctly in the host system, the aforementioned
> command is effectivly the install phase, while the rest is simply setting up the
> enviroment for the new system? I can certain get behind that.
Yes, the install phase mainly contains:
- build the system from config, only write to /gnu/store. (safe)
- deploy the system to target, overwrite /etc, /var/, etc.
and install the grub bootloader. (dangerous)
You can install it into a seperate partion (same as in the Manual),
it's more safe IMO.
next prev parent reply other threads:[~2016-10-01 1:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 1:09 Some questions regarding GuixSD dian_cecht
2016-09-30 8:18 ` Ludovic Courtès
2016-09-30 12:07 ` ng0
2016-09-30 16:07 ` Ludovic Courtès
2016-09-30 16:47 ` ng0
2016-09-30 19:50 ` dian_cecht
2016-09-30 19:46 ` dian_cecht
2016-10-01 1:50 ` 宋文武 [this message]
2016-10-01 2:19 ` dian_cecht
2016-10-01 3:42 ` 宋文武
2016-10-01 8:42 ` ng0
2016-10-02 13:14 ` 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
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=87vaxckfcc.fsf@member.fsf.org \
--to=iyzsong@member.fsf.org \
--cc=dian_cecht@zoho.com \
--cc=help-guix@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.
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).