unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Prikler <leo.prikler@student.tugraz.at>
To: bo0od <bo0od@riseup.net>, Bone Baboon <bone.baboon@disroot.org>
Cc: 47971@debbugs.gnu.org
Subject: bug#47971: Improve Guix commands for update/upgrade
Date: Fri, 23 Apr 2021 20:50:25 +0200	[thread overview]
Message-ID: <a040cb73ad8e5e1455f1335513ff32c217ea1b9a.camel@student.tugraz.at> (raw)
In-Reply-To: <a2878671-95f8-edc7-9a82-fb134e69d114@riseup.net>

Am Freitag, den 23.04.2021, 16:23 +0000 schrieb bo0od:
> Not really personal, Its about when there are new users these
> commands 
> looks horrible.
Sorry for informing you, but your sense for aesthetics is a very
personal thing.  If we really want to talk about UX, much more would be
gained by having a translatable GUI than through questionable command
renamings.

> You can call it personal when im saying use this X instead B while X
> and 
> B has the same bad approach or both are good. This is called personal
> e.g:
> 
> use upgrade instead of distro-upgrade = yeah very much is something
> not 
> really benefiting/different and personal.
> 
> but pull or update , reconfigure or system-upgrade...etc this is not 
> anymore personal as i have already explained in my reasoning above.

- guix pull: You "pull" a fresh set of package descriptions.  Note,
that you can't "push" package descriptions *yet*.
- guix upgrade: You "upgrade" a given user profile.
- guix system reconfigure: You "reconfigure" your "system" according to
the specifications made in some file.  Note, that this is not
inherently an upgrade -- it is perfectly fine only to change some
services, to add new ones, or to do all of those three at once.

Of course, there may come times, when you will have to explain to your
less tech-savvy family members or friends, who you've helped install
Guix, why upgrading all of your packages is such a tedious operation,
that involves this funny command line thing.  I've been there and done
that.  It all makes sense if you take a little time to
explain/understand it properly.

Regards,
Leo





      reply	other threads:[~2021-04-23 18:51 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
2021-04-23 16:23   ` bo0od
2021-04-23 18:50     ` Leo Prikler [this message]

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=a040cb73ad8e5e1455f1335513ff32c217ea1b9a.camel@student.tugraz.at \
    --to=leo.prikler@student.tugraz.at \
    --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).