public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: Benda Xu <heroxbd@gmail.com>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] Interest in GSoC w/ Gentoo
Date: Fri, 23 Feb 2018 22:51:10 +0900	[thread overview]
Message-ID: <CAMWv3tFaQAj444BtU0ruJo5Zh5AH3sqT=P6pMo-SfkVHEoBvzg@mail.gmail.com> (raw)
In-Reply-To: <CAAV=i8A9k0_nW3Sobehy9TGARKL6W9aXHOi_Y4rwHcjDAk09yQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1580 bytes --]

Hi Ethan,

Thank you for introducing nix.  It will be interesting to compare the
Microsoft windows registry with the centralized . nix configuration file.

Making Gentoo build reproducible and free of side-effects is a great
feature to have. Because it makes bug solving much easier.  There is a
demand for it.

The functional property of nix comes at the cost of violating Filesystem
Hierarchy Standard (FHS). If you come up with an atomic solution while
respecting FHS, it will be a big leap forward.

Yours,
Benda

2018/02/23 午後8:59 "Ethan Kiang" <chocopuff298@gmail.com>:

Hi!

I'm here with an update. I've went to check out more about nixOS, and how
their .nix configuration ideas could be applied to Gentoo. What I found out
was, one main advantage/selling point of nixOS is that it is takes a
functional approach to package/system management, resulting in no
side-effects (only have limited FP experience so sorry if that isn't
accurate description). I think we can use some of these ideas in the
creation of a configuration distribution system.


A few things to keep in mind however. Nix was built from the ground up to
be functional. Gentoo prides itself in being a meta-distribution, so I
think maybe it is possible to implement a functional configuration approach
too as a choice. However, this might be a big undertaking, requiring
perhaps major edits of portage or another pkg manager, which is maybe too
ambitious for the scope of GSoC. Also, maybe there isn't demand for
functional configuration on Gentoo.

Best,
Ethan

[-- Attachment #2: Type: text/html, Size: 2176 bytes --]

      reply	other threads:[~2018-02-23 13:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14 17:11 [gentoo-soc] Interest in GSoC w/ Gentoo Ethan Kiang
2018-02-21 15:14 ` Alice Ferrazzi
2018-02-23 11:58   ` Ethan Kiang
2018-02-23 13:51     ` Benda Xu [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMWv3tFaQAj444BtU0ruJo5Zh5AH3sqT=P6pMo-SfkVHEoBvzg@mail.gmail.com' \
    --to=heroxbd@gmail.com \
    --cc=gentoo-soc@lists.gentoo.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