From mboxrd@z Thu Jan 1 00:00:00 1970 From: Josh Holland 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 Message-ID: <87blxdqnb4.fsf@inv.alid.pw> References: <13483469.554170856.1564332865984.JavaMail.root@zimbra49-e8.priv.proxad.net> <2004384137.554259492.1564333244664.JavaMail.root@zimbra49-e8.priv.proxad.net> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:42428) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hs0dv-000874-So for help-guix@gnu.org; Mon, 29 Jul 2019 04:04:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hs0du-0001Bd-RJ for help-guix@gnu.org; Mon, 29 Jul 2019 04:04:27 -0400 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]:49425) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hs0ds-0000v5-JC for help-guix@gnu.org; Mon, 29 Jul 2019 04:04:26 -0400 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 28AA141C for ; Mon, 29 Jul 2019 04:04:18 -0400 (EDT) Received: from vega (highfield-nat.soton.ac.uk [152.78.0.22]) by mail.messagingengine.com (Postfix) with ESMTPA id 363BE380083 for ; Mon, 29 Jul 2019 04:04:17 -0400 (EDT) In-reply-to: <2004384137.554259492.1564333244664.JavaMail.root@zimbra49-e8.priv.proxad.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: help-guix@gnu.org 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