From: Ricardo Wurmus <rekado@elephly.net>
To: znavko@disroot.org
Cc: help-guix@gnu.org
Subject: Re: Where are suggestions or open discussions of Guix at large made?
Date: Tue, 08 Dec 2020 00:04:07 +0100 [thread overview]
Message-ID: <87r1o1nrq0.fsf@elephly.net> (raw)
In-Reply-To: <c0af88f634adedf0146491e86df1244c@disroot.org>
znavko@disroot.org writes:
> If you want popular comfortable OS on your home computer, that is not
> idea of Guix.
I must have been doing things wrong then. I find Guix System to be
exceptionally comfortable, and it’s the most popular OS on my home
computers ;)
@Yasuaki: Guix can be and is regularly extended with custom channels.
Since browsers and different variants of the kernel Linux are just
packages, channels can provide such packages, even when the official
Guix channels don’t provide them.
--
Ricardo
next prev parent reply other threads:[~2020-12-07 23:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 21:42 Where are suggestions or open discussions of Guix at large made? Yasuaki Kudo
2020-12-07 22:55 ` znavko
2020-12-07 23:04 ` Ricardo Wurmus [this message]
2020-12-08 0:41 ` zimoun
2020-12-08 2:20 ` Yasuaki Kudo
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=87r1o1nrq0.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=znavko@disroot.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).