From: zimoun <zimon.toutoune@gmail.com>
To: znavko@disroot.org, Yasuaki Kudo <yasu@yasuaki.com>,
help-guix <help-guix@gnu.org>
Subject: Re: Where are suggestions or open discussions of Guix at large made?
Date: Tue, 08 Dec 2020 01:41:36 +0100 [thread overview]
Message-ID: <86sg8h3z9b.fsf@gmail.com> (raw)
In-Reply-To: <c0af88f634adedf0146491e86df1244c@disroot.org>
Hi,
On Mon, 07 Dec 2020 at 22:55, znavko@disroot.org wrote:
> Guix repeats the idea of Nix, but realising it more preciously and
> elegantly.
The word “repeat” is incorrect here. It is more appropriated to say:
Guix is based on the idea of Nix or Guix applies similar ideas pioneered
by Nix.
The divergence is clear enough since the very beginning to not repeat
the confusing / wrong: “Guix is a fork of Nix implemented in Scheme”.
> It is hard to package some software you like for Guix,
It depends on how much Love are we ready to put in? :-)
> but forking guix breaking its elegance for just to install firmware,
> Oracle, Chrome and other stuff is not rational at all, i think.
The concept of channels avoids to fork and instead allow to extend. It
is possible to extend by adding packages, as the channel guix-past for
instance, or by adding subcommands, as the channel home-manager
illustrates for example.
> If you want popular comfortable OS on your home computer, that is not
> idea of Guix.
Popular is meaningless here. Comfortable, if not then I feel I am
failing and so please point your unpleasant experience and then let’s
see how to fix it. :-)
All the best,
simon
next prev parent reply other threads:[~2020-12-08 1:05 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
2020-12-08 0:41 ` zimoun [this message]
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=86sg8h3z9b.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=yasu@yasuaki.com \
--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).