unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Yasuaki Kudo <yasu@yasuaki.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Where are suggestions or open discussions of Guix at large made?
Date: Tue, 8 Dec 2020 11:20:22 +0900	[thread overview]
Message-ID: <8C609BE0-AE3A-4837-A058-66B77F93FC80@yasuaki.com> (raw)
In-Reply-To: <86sg8h3z9b.fsf@gmail.com>

Hi,

Of course, I agree with everything that's said here.  That's exactly why I am excited about Guix!   

I think it has a sound mechanism to fine-tune the degree of impurity one wishes to accept.

What I was thinking was maybe more organizational - is someone coming up to form a group or something 😄 that provides for a compromised (in-terms of accountability and license) yet convenient environment, akin to Ubuntu, using the fine mechanisms mentioned here?

It looks like Guix is creating a ripe environment for a service provider to do these things 😄

Cheers,
Yasu


> On Dec 8, 2020, at 09:51, zimoun <zimon.toutoune@gmail.com> wrote:
> 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


      reply	other threads:[~2020-12-08  2:21 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
2020-12-08  2:20     ` Yasuaki Kudo [this message]

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=8C609BE0-AE3A-4837-A058-66B77F93FC80@yasuaki.com \
    --to=yasu@yasuaki.com \
    --cc=help-guix@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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).