From: Pierre Neidhardt <mail@ambrevar.xyz>
To: "Konrad Hinsen" <konrad.hinsen@fastmail.net>,
"Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Profiles/manifests-related command line interface enhancements
Date: Thu, 07 Nov 2019 10:04:42 +0100 [thread overview]
Message-ID: <87d0e4oy51.fsf@ambrevar.xyz> (raw)
In-Reply-To: <m11ruk1640.fsf@ordinateur-de-catherine--konrad.home>
[-- Attachment #1: Type: text/plain, Size: 2270 bytes --]
Konrad Hinsen <konrad.hinsen@fastmail.net> writes:
> I agree. What's messy is how the concepts map to commands. How many Guix
> users understand that profiles are persistent environments, or
> environments ephemeral profiles? And how many understand what "guix
> environment -r" does exactly, and how it should be used? It took me a
> while to figure this out.
Yup! Before I got down to write the article, I must confess I had been
using Guix wrong for more than a year :p
> What we have is two commands (package and environment) each designed for
> one main usage pattern, plus options to get something else. But even
> those options don't overlap completely in functionality. For example,
> how do I make a profile with the dependencies of a package?
>
> The current discussion started with adding more commands for different
> specific usage patterns. If we go that route the mess will become worse.
Agreed.
> Me too :-) It's "guix package" that is the worst offender in my
> opinion. It does two distinct things: querying the package database and
> managing profiles. And now that we have "guix search" for queries, I'd
> like to see "guix package" go away, to be replaced by either "guix
> profile" for profile management, with as much overlap as possible in
> options with "guix environment", or by a single command that handles
> environments and profiles in a unified way.
I like this idea a lot!
> They do, but not very well in my opinion. I think everything meant to be
> shared, published, and maintained should be accessible by name in a
> database. A channel, for example.
>
> Some ideas that could make this possible (and convenient):
>
> - Better support for adding/managing channels at the user account
> level. Users shouldn't have to edit Guile code (unless they want to).
This is a great idea.
By the way, the same should be possible from the installer:
- Specify which channels you want to use.
- Specify which config.scm you want to use. Indeed, the config.scm
might rely on channels.
This way, the Guix installation process would boil down to the above 2
items, that is to say... 1 minute of the user time! Great, no?
Cheers!
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-11-07 9:04 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 16:37 Profiles/manifests-related command line interface enhancements Pierre Neidhardt
2019-10-24 9:00 ` Mark H Weaver
2019-10-24 9:32 ` Pierre Neidhardt
2019-10-24 16:28 ` Pierre Neidhardt
2019-10-24 16:42 ` Danny Milosavljevic
2019-10-24 18:16 ` Pierre Neidhardt
2019-10-24 19:23 ` Mark H Weaver
2019-10-24 20:04 ` Pierre Neidhardt
2019-10-24 21:35 ` Mark H Weaver
2019-10-25 9:29 ` Pierre Neidhardt
2019-10-31 11:38 ` Pierre Neidhardt
2019-11-03 14:18 ` Ludovic Courtès
2019-11-04 10:39 ` Pierre Neidhardt
2019-11-04 11:06 ` zimoun
2019-11-05 6:26 ` Konrad Hinsen
2019-11-05 8:35 ` Hartmut Goebel
2019-11-05 9:03 ` Konrad Hinsen
2019-11-05 9:09 ` Hartmut Goebel
2019-11-05 9:22 ` Pierre Neidhardt
2019-11-05 15:36 ` zimoun
2019-11-05 16:05 ` Konrad Hinsen
2019-11-06 12:09 ` zimoun
2019-11-07 13:07 ` Konrad Hinsen
2019-11-06 17:07 ` Ludovic Courtès
2019-11-06 22:21 ` Bengt Richter
2019-11-07 13:52 ` Konrad Hinsen
2019-11-06 16:35 ` Ludovic Courtès
2019-11-07 7:46 ` Konrad Hinsen
2019-11-07 9:04 ` Pierre Neidhardt [this message]
2019-11-07 11:14 ` Konrad Hinsen
2019-11-07 11:36 ` Pierre Neidhardt
2019-11-09 17:59 ` Ludovic Courtès
2019-11-10 9:36 ` Konrad Hinsen
2019-11-11 15:56 ` A better XML, config is code (was Re: Profiles/manifests-related command line...) Giovanni Biscuolo
2019-11-13 15:28 ` Konrad Hinsen
2019-11-12 8:55 ` Profiles/manifests-related command line interface enhancements Andy Wingo
2019-11-12 20:07 ` Konrad Hinsen
2019-11-13 20:58 ` Bengt Richter
2019-11-16 22:02 ` Ludovic Courtès
2019-11-17 10:44 ` Konrad Hinsen
2019-11-18 14:25 ` zimoun
2019-11-19 10:24 ` Konrad Hinsen
2019-11-23 17:10 ` Ludovic Courtès
2019-11-25 11:06 ` Konrad Hinsen
2019-11-26 9:51 ` On DSLs Ludovic Courtès
2019-12-02 19:05 ` zimoun
2019-12-02 19:11 ` Julien Lepiller
2019-12-03 10:19 ` Konrad Hinsen
2019-12-03 14:12 ` Ricardo Wurmus
2019-12-03 15:46 ` zimoun
2019-12-04 6:33 ` Bengt Richter
2019-12-10 16:26 ` Ludovic Courtès
2019-12-08 8:48 ` Konrad Hinsen
2019-12-03 10:26 ` Konrad Hinsen
2019-12-03 12:00 ` zimoun
2019-11-11 14:13 ` Profiles/manifests-related command line interface enhancements Hartmut Goebel
2019-11-16 22:27 ` Ludovic Courtès
2019-11-17 11:30 ` Konrad Hinsen
2019-11-18 14:40 ` zimoun
2019-12-22 19:40 ` Andreas Enge
2019-12-22 20:39 ` Pjotr Prins
2019-11-18 14:15 ` zimoun
2019-11-26 9:36 ` Ludovic Courtès
2019-11-06 16:42 ` Ludovic Courtès
2019-11-07 12:57 ` zimoun
2019-11-17 10:35 ` Package inputs in manifests Ludovic Courtès
2019-11-17 23:11 ` Bengt Richter
2019-11-18 17:14 ` zimoun
2019-11-23 14:05 ` Ludovic Courtès
2019-11-24 5:49 ` Bengt Richter
2019-11-24 7:17 ` Timothy Sample
2019-11-25 3:42 ` Bengt Richter
2019-11-18 16:18 ` zimoun
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=87d0e4oy51.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=guix-devel@gnu.org \
--cc=konrad.hinsen@fastmail.net \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.