From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: ~/.guix-profile/manifest usage with "guix package -m [manifest]"
	/ "guix pack -m [manifest]" etc..
Date: Tue, 02 Oct 2018 14:46:13 +0200
Message-ID: <87sh1oms8a.fsf@gnu.org>
References: <DB6P18901MB00224167FCF569A5EA89558CDB160@DB6P18901MB0022.EURP189.PROD.OUTLOOK.COM>
	<87h8ic36ix.fsf@gnu.org> <cucmurxzaj5.fsf@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:45260)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1g7K4J-0008UL-EX
	for guix-devel@gnu.org; Tue, 02 Oct 2018 08:46:28 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1g7K4D-0000C7-KU
	for guix-devel@gnu.org; Tue, 02 Oct 2018 08:46:25 -0400
In-Reply-To: <cucmurxzaj5.fsf@gmail.com> (George Clemmer's message of "Mon, 01
	Oct 2018 16:17:50 -0400")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: George Clemmer <myglc2@gmail.com>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>, YOANN P <yoann_mac_donald@hotmail.com>

Hello,

George Clemmer <myglc2@gmail.com> skribis:

> YOANN hit an error when trying to do 'guix package -m
> ~/.guix-profile/manifest'. Why would one want to do this? Maybe to
> (re)produce a configuration previously reached by a series of 'guix
> package -i' operations?

I agree this would be nice, but be aware that this is not quite possible
because those files don=E2=80=99t have enough information to rebuild packag=
es.

Starting from a few weeks/months ago, ~/.guix-profile/manifest records
upstream VCS information, like this:

     ("libreoffice"
      "6.1.2.1"
      "out"
      "/gnu/store/y4l3r7nh0dg3d8qaifz96ffab4jpjl3s-libreoffice-6.1.2.1"
      (propagated-inputs ())
      (search-paths ())
      (properties
        (provenance
          (repository
            (version 0)
            (url "https://git.savannah.gnu.org/git/guix.git")
            (branch "master")
            (commit
              "f8e710684e5c3f866413dff825ba17bdffceac5d")))))

With this info and with inferiors and channels, it becomes possible to
rebuild the package (if we make simplifying assumptions.)

So I understand the need and agree that it would be nice.  But for now,
I strongly recommend =E2=80=9Cmanifests as passed to =E2=80=98guix package =
-m=E2=80=99=E2=80=9D because
they=E2=80=99re much more expressive, especially with the introduction of t=
he
inferior API:

  https://issues.guix.info/issue/32759

HTH!

Ludo=E2=80=99.