From: Alex Kost <alezost@gmail.com>
To: "Taylan Ulrich \"Bayırlı/Kammer\"" <taylanbayirli@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Reorganizing guix package commands
Date: Tue, 19 Apr 2016 13:37:42 +0300 [thread overview]
Message-ID: <87d1plj349.fsf@gmail.com> (raw)
In-Reply-To: <871t62555i.fsf@T420.taylan> ("Taylan Ulrich \=\?utf-8\?Q\?\=5C\=22Bay\=C4\=B1rl\=C4\=B1\=2FKammer\=5C\=22\=22's\?\= message of "Tue, 19 Apr 2016 11:17:29 +0200")
Taylan Ulrich "Bayırlı/Kammer" (2016-04-19 12:17 +0300) wrote:
> Alex Kost <alezost@gmail.com> writes:
>
>> Here is the summary of the changes I think it would be good to have:
>>
>> | Replace this: | With this: |
>> |-----------------------------------+-----------------------------------|
>> | guix build | guix package build |
>> | guix edit | guix package definition¹ |
>> | guix import | guix package import |
>> | guix lint | guix package lint |
>> | guix refresh | guix package refresh |
>> | guix package --show | guix package show |
>> | guix package --search | guix package search |
>> | guix package --list-available | guix package list |
>> |-----------------------------------+-----------------------------------|
>> | guix package --list-generations | guix profile --list-generations |
>> | guix package --list-installed | guix profile --list-installed |
>> | guix package --delete-generations | guix profile --delete-generations |
>> | guix package --switch-generations | guix profile --switch-generations |
>> | guix package --roll-back | guix profile --roll-back |
>> | guix package --manifest | guix profile --manifest |
>>
>> ¹ "edit" name is confusing: <http://bugs.gnu.org/22587>
>
> How about "view"? ("Definition" is so long.)
I prefer "definition", but it's just my opinion. Maybe we can use the
same feature as some other software use, like you can write: "ip
address" or "ip addr" or even "ip a". I.e., if some portion of
characters defines a subcommand name unambiguously, it's ok to use. So
this could become "guix package def" or "guix package d" if there will
be no other subcommands beginning with "d".
I think it would be a great feature (I already wish to write "guix env"
or "guix sy re" :-)). I think it is for a separate thread though.
>> Maybe instead of --list-generations and others, these options should
>> transform into subcommands (list-generations) of "guix profile".
>
> Yeah, seems more consistent.
>
> I don't have a strong opinion on this whole thing but I think a clear
> and logical categorization like the above would be a good base. One
> could then add abbreviations on top of it like:
>
> guix install -> guix package install
>
> Hmm, or does 'install' belong to 'profile'? Or should the whole thing
> be called 'guix profile add'? "Install" kinda implies that something
> new will be installed into the system, rather than just some symlinks
> shuffled. (One can see the building or downloading as a special case /
> transparent handling of the case where the package to be added to the
> profile is not in the store yet.)
Yes, this is controversial. I think it would be clean to separate
profile stuff into a separate command ("guix profile"). As for adding
"guix package install/remove", I don't really know.
> BTW if it is to become e.g. 'guix profile add', then combining an
> add/remove in one transaction (if it's important to keep that feature)
I think this is a very important feature.
> could look like:
>
> guix package add foo bar -- remove baz bat
To be honest I don't like it. There is also "upgrade" which can be
performed along with install and remove.
But I like "--add" instead of or along with (as they may just co-exist
and do the same thing) "--install" in a potential "guix profile"
command.
--
Alex
next prev parent reply other threads:[~2016-04-19 10:37 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 8:57 Reorganizing guix package commands Alex Kost
2016-04-18 16:10 ` John Darrington
2016-04-19 8:01 ` Alex Kost
2016-04-18 17:20 ` Ludovic Courtès
2016-04-18 21:50 ` myglc2
2016-04-19 5:17 ` John Darrington
2016-04-19 12:57 ` myglc2
2016-04-19 13:03 ` Thompson, David
2016-04-19 13:35 ` John Darrington
2016-04-19 13:51 ` myglc2
2016-04-19 15:24 ` Ludovic Courtès
2016-04-19 10:47 ` Alex Kost
2016-04-19 10:58 ` Ricardo Wurmus
2016-04-19 12:45 ` myglc2
2016-04-19 7:52 ` Alex Kost
2016-04-19 9:17 ` Taylan Ulrich Bayırlı/Kammer
2016-04-19 10:37 ` Alex Kost [this message]
2016-04-19 9:23 ` Hartmut Goebel
2016-04-19 10:16 ` Alex Kost
2016-04-19 14:39 ` John Darrington
2016-04-19 13:00 ` myglc2
2016-04-19 13:43 ` Ricardo Wurmus
2016-04-19 14:29 ` myglc2
2016-04-19 13:55 ` Ricardo Wurmus
2016-04-19 15:52 ` Ludovic Courtès
2016-04-19 19:56 ` Christopher Allan Webber
2016-04-20 3:45 ` myglc2
2016-04-20 5:34 ` John Darrington
2016-04-20 8:52 ` Alex Kost
2016-04-20 17:05 ` myglc2
2016-04-20 8:29 ` Alex Kost
2016-04-20 9:46 ` Taylan Ulrich Bayırlı/Kammer
2016-04-20 21:45 ` Ludovic Courtès
2016-04-21 12:34 ` myglc2
2016-04-21 5:20 ` John Darrington
2016-04-20 9:29 ` Taylan Ulrich Bayırlı/Kammer
2016-04-21 2:49 ` Efraim Flashner
2016-04-21 7:10 ` Taylan Ulrich Bayırlı/Kammer
2016-04-18 21:13 ` Hartmut Goebel
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=87d1plj349.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=taylanbayirli@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.
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.