From: Bone Baboon via Bug reports for GNU Guix <bug-guix@gnu.org>
To: bo0od <bo0od@riseup.net>
Cc: 47971@debbugs.gnu.org
Subject: bug#47971: Improve Guix commands for update/upgrade
Date: Fri, 23 Apr 2021 11:16:40 -0400 [thread overview]
Message-ID: <878s592fqf.fsf@disroot.org> (raw)
In-Reply-To: <d6318446-4b47-e68d-0ea6-e0755dd52e2b@riseup.net>
bo0od writes:
> The current commands used to make sure everything updated are not
> friendly to type nor to memorize
The name of package management commands seems like it would largely be
personal preference.
Each person using Guix could customize the commands to their own
preferences using Bash aliases or an equivalent for the shell they are
using. For Bash refer to the Aliases section of it's info
documentation.
> - pull -> update or refresh
> - upgrade -> can be kept or package-upgrade
> - reconfigure /etc/config.scm -> dist-upgrade or distro-upgrade or
> system-upgrade
For command names there are many package managers that you can look to
for inspiration. Here are some examples:
* Gentoo - emerge
* OpenBSD - pkg
* Void - xbps
* Alpine - apk
* Debian - apt
* Arch - pacam or paru
* Fedora - dnf
> 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
This could also be done with shell aliases.
next prev parent reply other threads:[~2021-04-23 18:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 13:41 bug#47971: Improve Guix commands for update/upgrade bo0od
2021-04-23 14:15 ` Christopher Baines
2021-04-23 14:46 ` bo0od
2021-04-23 15:16 ` Bone Baboon via Bug reports for GNU Guix [this message]
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=878s592fqf.fsf@disroot.org \
--to=bug-guix@gnu.org \
--cc=47971@debbugs.gnu.org \
--cc=bo0od@riseup.net \
--cc=bone.baboon@disroot.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).