From: ludo@gnu.org (Ludovic Courtès)
To: George Clemmer <myglc2@gmail.com>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>,
YOANN P <yoann_mac_donald@hotmail.com>
Subject: Re: ~/.guix-profile/manifest usage with "guix package -m [manifest]" / "guix pack -m [manifest]" etc..
Date: Thu, 11 Oct 2018 15:44:12 +0200 [thread overview]
Message-ID: <87murk4mz7.fsf@gnu.org> (raw)
In-Reply-To: <cucwoqpq4ja.fsf@gmail.com> (George Clemmer's message of "Wed, 10 Oct 2018 10:07:05 -0400")
Hi,
George Clemmer <myglc2@gmail.com> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Hello,
>>
>> Ricardo Wurmus <rekado@elephly.net> skribis:
>>
> [...]
>>> You can put this in a file “manifest-to-manifest.scm” and run it like
>>> this from a Guix source checkout:
>>>
>>> ./pre-inst-env guile -s manifest-to-manifest.scm /path/to/.guix-profile > my-manifest.scm
>>
>> I like how the script’s name highlights the naming inconsistency. :-)
>
> ... and that we should consider renaming one of these "manifests" ;-)
>
>>> You can then proceed to install the generated manifest with:
>>>
>>> guix package -m my-manifest.scm -p /path/to/new/.guix-profile
>>>
>>> If that’s what you’re looking for I suppose we could find a place for
>>> something like that under the umbrella of “guix package”.
>>
>> The problem, as I see it, is that this might give a false impression
>> that both “manifests” are entirely equivalent, which is not the case.
>
> This "false impression" is caused by the "naming inconsistency" (above)
> rather that by the proposed function, isn't it?
True, the naming inconsistency is probably the root problem. Now, it
should be said that ~/.guix-profile/manifest is not documented anywhere,
so people fiddling with it are on their own anyway. :-)
>> I sympathize with George’s idea of making it easier to move from the
>> incremental style to the declarative style, but I wonder if we should go
>> beyond suggesting to basically copy the package names shown in “guix
>> package -I” to the manifest file.
>
> Does this mean to have "manifest-to-manifest.scm" add any non-default
> (in the current Guix version) package outputs and versions to the
> package specifications produced? Or something else?
manifest-to-manifest.scm works matching package names/versions, which
are ambiguous compared to store items. This ambiguity means that the
“conversion” that manifest-to-manifest.scm performs is necessarily
lossy.
Ludo’.
prev parent reply other threads:[~2018-10-11 13:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 19:55 ~/.guix-profile/manifest usage with "guix package -m [manifest]" / "guix pack -m [manifest]" etc YOANN P
2018-09-26 10:19 ` Ludovic Courtès
2018-09-27 20:03 ` YOANN P
2018-09-27 21:49 ` Alex Kost
2018-09-29 16:33 ` Ludovic Courtès
2018-10-01 20:17 ` George Clemmer
2018-10-01 22:40 ` YOANN P
2018-10-02 12:46 ` Ludovic Courtès
2018-10-02 16:55 ` George Clemmer
2018-10-02 20:41 ` Ricardo Wurmus
2018-10-02 21:35 ` George Clemmer
2018-10-08 12:26 ` Ludovic Courtès
2018-10-10 14:07 ` George Clemmer
2018-10-11 13:44 ` Ludovic Courtès [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87murk4mz7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=myglc2@gmail.com \
--cc=yoann_mac_donald@hotmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.