From: bo0od <bo0od@riseup.net>
To: Christopher Baines <mail@cbaines.net>
Cc: 47971@debbugs.gnu.org
Subject: bug#47971: Improve Guix commands for update/upgrade
Date: Fri, 23 Apr 2021 14:46:28 +0000 [thread overview]
Message-ID: <11bff206-c709-e633-67ac-390bb65ffd03@riseup.net> (raw)
In-Reply-To: <87pmylgk8e.fsf@cbaines.net>
> I don't get what you mean when you say pull is actually the opposite of
> push? That's true in the sense of the words, but how does that relate to
> Guix?
git pull , git push -> both are making sense
guix pull, but no guix push -> doesnt make sense as there is no relation
between pull and other used commands. (thus i suggested to use known
linked-terms like update,upgrade...etc)
> You can "downgrade" (switch to using an older Guix/software) by
> reconfiguring, so I wouldn't like to see that operation referred to as
> an upgrade (as it's not always)
I see, for example it can be made as upgrade command to always read
configurations which are only intended for upgrading the system and if
you want to use downgrade then it will read configurations only intended
for downgrading the system. (either by using the same config.scm or each
command point to separated config.scm like upgrade.scm and downgrade.scm...)
by this can run system-upgrade , system-downgrade or
dist-upgrade/downgrade..etc
Maybe there are better solutions like better terms or technical
solutions someone can come up with to make things better than the
current situation.
Christopher Baines:
>
> bo0od <bo0od@riseup.net> writes:
>
>> 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.
>
> guix pull usually does a git pull under the hood and then builds guix
> from that updated repository.
>
> I don't get what you mean when you say pull is actually the opposite of
> push? That's true in the sense of the words, but how does that relate to
> Guix?
>
>> - 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
>
> I think update is OK, although I think pull is OK too. refresh is
> already taken.
>
>> - upgrade -> can be kept or package-upgrade
>> - reconfigure /etc/config.scm -> dist-upgrade or distro-upgrade or
>> system-upgrade
>
> You can "downgrade" (switch to using an older Guix/software) by
> reconfiguring, so I wouldn't like to see that operation referred to as
> an upgrade (as it's not always).
>
next prev parent reply other threads:[~2021-04-23 14:47 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 [this message]
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=11bff206-c709-e633-67ac-390bb65ffd03@riseup.net \
--to=bo0od@riseup.net \
--cc=47971@debbugs.gnu.org \
--cc=mail@cbaines.net \
/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).