From: ng0 <ngillmann@runbox.com>
To: "Ludovic Courtès" <ludo@gnu.org>, dian_cecht@zoho.com
Cc: help-guix@gnu.org
Subject: Re: Some questions regarding GuixSD
Date: Fri, 30 Sep 2016 12:07:22 +0000 [thread overview]
Message-ID: <87eg418ubp.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87zimpssv3.fsf@gnu.org>
Hi,
I hope you don't mind if I add to this some lines.
Ludovic Courtès <ludo@gnu.org> writes:
> Hi,
>
> dian_cecht@zoho.com skribis:
>
>> 1) Is there any way to prevent a package from being installed at all?
>
> Only packages that you want are “installed”, in the sense that only
> packages that you explicitly ask for are available in your user profile.
>
> The /gnu/store directory may contain other packages, but you don’t have
> to worry about that.
>
>> 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.
>
>> 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!
>
>> 4) Is GnuNET integration already working?
>
> No.
It's a bit of a stretch (in time), but I've applied for funding
yesterday and one of the 3 ideas is to push gnunet integration further,
to aid the live-system I am working on. I say 'stretch' because this is
a topic which requires some preparing contributions and then lots of
testing and diving deeper into the core of Guix :)
So if all goes well, I know around december if I qualified with my idea
for funding and can almost worry-free hack on this for another 6
months.
It's like Google Summer of Code, only a bit longer. I'll very optimistic
and say that my internal documented goal for basic gnunet-filesystem
integration for guix is summer / autumn 2017.
>> 5) How do I install Guix for a nonroot account in another distro?
>
> First you install it as root, as described in the installation
> instructions at <https://www.gnu.org/software/guix/download/>.
> Then all the users on that system, root or not, can use it.
>
>> I'm also curious what the current plans are for Guix/GuixSD are.
>
> The ‘ROADMAP’ file lists remaining features or issues that need to be
> addressed before 1.0. If everything goes well, 1.0 will be ready within
> 6 months or so.
>
> HTH!
>
> Ludo’.
>
>
--
ng0
#.endofsubmission.
next prev parent reply other threads:[~2016-09-30 12:07 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 [this message]
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 ` 宋文武
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=87eg418ubp.fsf@we.make.ritual.n0.is \
--to=ngillmann@runbox.com \
--cc=dian_cecht@zoho.com \
--cc=help-guix@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.
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).