From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: help-guix@gnu.org
Subject: Re: boost 1-60
Date: Fri, 08 Jan 2016 11:10:09 +0100 [thread overview]
Message-ID: <87ziwgl6v2.fsf@gnu.org> (raw)
In-Reply-To: <20160108023811.GB26535@jasmine> (Leo Famulari's message of "Thu, 7 Jan 2016 21:38:11 -0500")
Leo Famulari <leo@famulari.name> skribis:
> On Thu, Jan 07, 2016 at 04:30:02PM -0800, carl hansen wrote:
[...]
>> I did guix refresh
>> and I see 200 packages can be updated. Can that be automated? It's kind of
>> annoying to get not up to date packages, especially to obsessive/compulsive
>> geeks.
>
> `guix refresh` doesn't need to be used here. Use `guix package` for
> installing, upgrading, and removing software.
And ‘guix pull’ to update the package definitions available at your
site (similar to ‘apt-get update’.)
‘guix refresh’ is a helper for Guix developers, as mentioned in the
manual (info "(guix) Invoking guix refresh").
Ludo’.
next prev parent reply other threads:[~2016-01-08 10:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 23:33 boost 1-60 carl hansen
2016-01-07 22:53 ` Ben Woodcroft
2016-01-08 0:30 ` carl hansen
2016-01-08 2:38 ` Leo Famulari
2016-01-08 10:10 ` Ludovic Courtès [this message]
2016-01-08 21:34 ` Andreas Enge
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=87ziwgl6v2.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
/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.
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).