From: Mekeor Melire <mekeor.melire@gmail.com>
To: Job Hernandez <hdezlara17@protonmail.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: guixSD
Date: Thu, 20 Jul 2017 01:27:17 +0200 [thread overview]
Message-ID: <87tw283t4a.fsf@gmail.com> (raw)
In-Reply-To: <70OkKWadjDdxuCAy2JvDSA3e4W6-4Ugp0Y3ElqwJecWhAdBYEdVLt5Mhqjs0B4h7yVy7uF-W_DUyhZEHX5a6Kp1mrQvjL8HL5H5-qk9PfvA=@protonmail.com>
Job Hernandez <hdezlara17@protonmail.com> writes:
> Hi, on the manual it says that the guixSD is not production ready. Im eager to start using this as my primary operating system-- when will it be production ready?
For completeness, this is what the manual states at chapter 6.1.1:
> the Guix System Distribution (GuixSD) is not production-ready. It may
> contain bugs and lack important features.
I guess we have to wait for version 1.0 to be released so that GuixSD
can be called "stable". Personally, I don't know exactly when this is
expected to happen.
Anyway, GuixSD is already "usable". I personally even use it for
"production". And indeed it contains bugs sometimes and lacks important
features sometimes. But I can live with that.
If you want to find out if you can live with these issues, you could (1)
try out Guix package manager on top of another (so-called "foreign")
GNU+Linux distribution; (2) try out GuixSD inside a virtual machine; (3)
try GuixSD on a real computer.
Good luck :)
--
mekeor ~ EDD3 DFFA 76F6 11C0 145F 9A99 AC85 BAD8 A2F8 C868
next prev parent reply other threads:[~2017-07-19 23:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 20:45 guixSD Job Hernandez
2017-07-19 23:27 ` Mekeor Melire [this message]
2017-07-20 14:40 ` guixSD Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2017-02-16 10:21 guixsd Isorkin
2017-03-02 13:02 ` guixsd Ricardo Wurmus
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=87tw283t4a.fsf@gmail.com \
--to=mekeor.melire@gmail.com \
--cc=hdezlara17@protonmail.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).