[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ~/.guix-profile/manifest usage with "guix package -m [manifest]" / "

From: Ludovic Courtès
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
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)


George Clemmer <address@hidden> 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’t have enough information to rebuild packages.

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

      (propagated-inputs ())
      (search-paths ())
            (version 0)
            (url "";)
            (branch "master")

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 “manifests as passed to ‘guix package -m’” because
they’re much more expressive, especially with the introduction of the
inferior API:



reply via email to

[Prev in Thread] Current Thread [Next in Thread]