From: bo0od <bo0od@riseup.net>
To: 47971@debbugs.gnu.org
Subject: bug#47971: Improve Guix commands for update/upgrade
Date: Fri, 23 Apr 2021 13:41:11 +0000 [thread overview]
Message-ID: <d6318446-4b47-e68d-0ea6-e0755dd52e2b@riseup.net> (raw)
Hi There,
The current commands used to make sure everything updated are not
friendly to type nor to memorize, Current commands:(i dunno if i missed
more)
guix pull
guix upgrade
sudo guix reconfigure /etc/config.scm
There is no relation can be drawn from using these commands:
- pull: Is actually the opposite of push which is a git command and it
make sense in git atmosphere/usage.
- upgrade: This is the only good one as this is very common term used
within distros or actually most of the operating systems generally.
- reconfigure /etc/config.scm: hmm...
There are many ways we can improve this by using different better terms
which can be easily memorized and even linked e.g: (These are just
examples, If there are any better terms you can come with sure why not)
- pull -> update or refresh
- upgrade -> can be kept or package-upgrade
- reconfigure /etc/config.scm -> dist-upgrade or distro-upgrade or
system-upgrade
----
OR There is another approach some distros taking which is using
shortcuts to only letters e.g
pull -> p or -p
upgrade -> u or -u
reconfigure -> re or -re
as a one world for memory "pure" (any other letters can be used as well)
ThX!
next reply other threads:[~2021-04-23 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 13:41 bo0od [this message]
2021-04-23 14:15 ` bug#47971: Improve Guix commands for update/upgrade Christopher Baines
2021-04-23 14:46 ` bo0od
2021-04-23 15:16 ` Bone Baboon via Bug reports for GNU Guix
2021-04-23 16:23 ` bo0od
2021-04-23 18:50 ` Leo Prikler
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=d6318446-4b47-e68d-0ea6-e0755dd52e2b@riseup.net \
--to=bo0od@riseup.net \
--cc=47971@debbugs.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 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).