From: "Raghav Gururajan" <raghavgururajan@disroot.org>
To: Leo Prikler <leo.prikler@student.tugraz.at>, guix-devel@gnu.org
Subject: Re: Thoughts on making Guix even better
Date: Sun, 01 Mar 2020 10:26:00 +0000 [thread overview]
Message-ID: <4b94b57c9165e519542a5bb4748b91d0@disroot.org> (raw)
In-Reply-To: <131d7d47e8e77a426a28013be0e063ff9de735a9.camel@student.tugraz.at>
Hello Leo!
> This is not as much a guix package vs. guix system issue as it is an
> issue of explicit manifests against implicit ones. If you use guix
> package with manifests and without inferiors, you will have the same
> problem. Likewise, you can use inferiors in your config.scm to
> mitigate some of those issues. At least it works for the kernel, but
> it should in theory also work for packages.
I see.
> PS: What you're envisioning is probably a front-end, that obscures the
> very existence of a config.scm by managing one that is just as verbose
> as guix-generated manifests are. However, this is not really a
> solution as it fails to address the need for a (human-readable) initial
> configuration. The interface would also be a pain to deal with as each
> service comes with its own configuration record allowing arbitrary lisp
> expressions that one would have to write on the command line.
I think we can still maintain the guix way of doing config.scm and also bring modularity. My thought is, what if we could split the operating-system procedures into smaller procedures, such as, kernel, system-wide packages, services etc. into separate procedures? So if a user passes the procedure name to the `guix system reconfigure` command, then only that procedure is reconfigured. For example, we can reconfigure kernel of the system without reconfiguring packages and services.
What do you think?
Regards,
RG.
next prev parent reply other threads:[~2020-03-01 10:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <24c65c56c37b309c108f75fb9e3e4681866e7fac.camel@student.tugraz.at>
2020-02-23 17:14 ` Thoughts on making Guix even better Leo Prikler
2020-03-01 10:26 ` Raghav Gururajan [this message]
2020-02-23 2:49 Raghav Gururajan
2020-02-23 20:28 ` Jonathan Frederickson
2020-03-08 20:54 ` Ludovic Courtès
2020-03-09 6:18 ` Gábor Boskovits
2020-03-09 7:28 ` Konrad Hinsen
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=4b94b57c9165e519542a5bb4748b91d0@disroot.org \
--to=raghavgururajan@disroot.org \
--cc=guix-devel@gnu.org \
--cc=leo.prikler@student.tugraz.at \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).