From: hub.lombard@free.fr
To: Josh Holland <josh@inv.alid.pw>
Cc: 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 14:13:34 +0200 (CEST) [thread overview]
Message-ID: <1577434376.564215669.1564402414332.JavaMail.root@zimbra49-e8.priv.proxad.net> (raw)
In-Reply-To: <87wog113j7.fsf@inv.alid.pw>
Hi Josh :-)
----- Mail original -----
De: "Josh Holland" <josh@inv.alid.pw>
À: "hub lombard" <hub.lombard@free.fr>
Cc: help-guix@gnu.org
Envoyé: Lundi 29 Juillet 2019 13:30:36
Objet: Re: A 'guix pull' option for 'manifest.scm' to be used in the next update
Hi Hubert,
hub.lombard@free.fr writes:
> So maybe (I'm not sure) I can try, considering the path of my manifest.scm:
>
> $ guix pull && guix package -m ~/.config/guix/manifest.scm -u
Yep, if that's the right path to where you saved your manifest file.
(Note that the -u option, upgrade, takes an optional argument, a regexp
matching which packages to act on. I prefer to explicitly pass in
`-u.` to match anything since I normally run this command from my shell
history, and I can then just add any other options I want without them
being interpreted as an argument to -u.)
\o/ it seems very interesting... Feeling like a lucky user to get note about this option.
And I'll try it on my own command-line for the next update.
> Otherwise, unless I have to move my file to another place?
You can save the manifest file wherever you want, since you pass the
path into `guix package` with the -m option it'll always be able to find
it.
... OK, good to know. I'm learning something more!
Thanks,
Josh
Thank you!
Hubert
prev parent reply other threads:[~2019-07-29 12:13 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
2019-07-29 10:58 ` hub.lombard
2019-07-29 11:30 ` Josh Holland
2019-07-29 12:13 ` hub.lombard [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=1577434376.564215669.1564402414332.JavaMail.root@zimbra49-e8.priv.proxad.net \
--to=hub.lombard@free.fr \
--cc=help-guix@gnu.org \
--cc=josh@inv.alid.pw \
/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).