From: Josh Holland <josh@inv.alid.pw>
To: help-guix@gnu.org
Subject: Re: A 'guix pull' option for 'manifest.scm' to be used in the next update
Date: Mon, 29 Jul 2019 09:04:15 +0100 [thread overview]
Message-ID: <87blxdqnb4.fsf@inv.alid.pw> (raw)
In-Reply-To: <2004384137.554259492.1564333244664.JavaMail.root@zimbra49-e8.priv.proxad.net>
Hi Hubert,
hub.lombard@free.fr writes:
> In order for 'manifest.scm' to be used in the next update, should I do something like this:
>
> $ guix pull -p, --profile=PROFILE
>
> (using PROFILE instead of ~/.config/guix/current)
`guix pull` is not the command that you should be passing your manifest
file to. If you are familiar with Debian-based distros, then `guix
pull` is (somewhat) analogous to `apt update`: it gets updated package
definitions (and also updates the guix program itself) but doesn't make
any changes to packages you have installed.
Also, I think you have misunderstood what the PROFILE option is
referring to. A "profile" in Guix is a collection of packages. Usually
you'll have a single profile for each user, and perhaps some ad-hoc
profiles created behind the scenes by running `guix environment`. In
several months of running Guix, I've never needed to use the --profile
option.
To actually use the manifest, you want to pass it to `guix package`.
For example, here's the command I normally run to upgrade everything:
$ guix pull && guix package -m ~/guix-packages.scm -u .
Thanks,
Josh
next prev parent reply other threads:[~2019-07-29 8:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <13483469.554170856.1564332865984.JavaMail.root@zimbra49-e8.priv.proxad.net>
2019-07-28 17:00 ` A 'guix pull' option for 'manifest.scm' to be used in the next update hub.lombard
2019-07-29 8:04 ` Josh Holland [this message]
2019-07-29 10:58 ` hub.lombard
2019-07-29 11:30 ` Josh Holland
2019-07-29 12:13 ` hub.lombard
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=87blxdqnb4.fsf@inv.alid.pw \
--to=josh@inv.alid.pw \
--cc=help-guix@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.
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).