From: zimoun <zimon.toutoune@gmail.com>
To: elaexuotee@wilsonb.com
Cc: guix-devel@gnu.org
Subject: Re: Using --manfistest with <profile>/manifest files
Date: Tue, 16 Jun 2020 11:09:49 +0200 [thread overview]
Message-ID: <86eeqfs7fm.fsf@gmail.com> (raw)
In-Reply-To: <3IMA7W1L0NQCB.3GCC1X0HBIALO@wilsonb.com>
Dear,
On Mon, 15 Jun 2020 at 19:08, elaexuotee@wilsonb.com wrote:
> I went ahead and read through the threads that Pierre shared in a different
> reply. For posterity and to collect my own thoughts, let me see if I can
> distill the discussion so far:
[...]
> If the answer to the final question above is no, then that seems like a much
> larger problem. However, if the answer is yes, then I would naively expect
> profile reification to be mostly a matter of collecting together all the
> sources of input that define a profile. Does forward-compatibility make this
> less straightforward than I am thinking? What else am I missing?
Thank you for your inputs.
From my understanding, what you are proposing is a variant of what
Pierre proposes. To be precise, at Guix Days, Pierre and I discussed to
change a bit the format of <profile>/manifest in order to unify the
current situation of "manifest.scm" (code evaluated) and
"<profile>/manifest" (flat data); as Pierre explained elsewhere in this
thread. The change of internals will not happen, IMHO, because dealing
with the general case adds too much burden, and the use-case discussed
here -- recreate the exact same profile from another imperative profile
-- does not deserve so much attention, again IMHO.
From my point of view, it is a technical problem of internal
representation and then of UI. And Ludo expressed that he is not in
favor for such internal change, because a lot of reasons he explained
elsewhere (argh! I do not like what I am doing here: be imprecise
without citing exactly, anyway!).
The best, if I understand correctly, is simply to robustify the Pierre's
script and provide a clean '--export-manifest' from a profile which
should be an approximation.
>> Sorry I am too lazy to search, but I think I remember that at the time
>> Pierre sent -- probably in the mega thread :-) -- a small script to
>> extract relevant information from <profile>/manifest; the preliminary
>> for '--export-manifest'. :-)
>
> Perhaps you are thinking of Pierre's script here?
> https://lists.gnu.org/archive/html/guix-devel/2020-02/msg00154.html
Yes.
All the best,
simon
prev parent reply other threads:[~2020-06-16 9:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 1:40 Using --manfistest with <profile>/manifest files elaexuotee
2020-06-13 20:36 ` Ludovic Courtès
2020-06-14 10:17 ` Pierre Neidhardt
2020-06-14 15:24 ` Ludovic Courtès
2020-06-15 7:52 ` Pierre Neidhardt
2020-06-16 9:44 ` Ludovic Courtès
2020-06-15 8:08 ` zimoun
2020-06-16 9:46 ` Ludovic Courtès
2020-06-16 11:33 ` elaexuotee
2020-06-16 13:42 ` zimoun
2020-06-17 0:45 ` elaexuotee
2020-06-17 7:58 ` how to "guix pack" a profile? zimoun
2020-06-18 9:20 ` elaexuotee
2020-06-18 23:49 ` zimoun
2020-06-19 2:52 ` elaexuotee
2020-06-19 8:30 ` zimoun
2020-06-19 12:34 ` elaexuotee
2020-06-19 15:38 ` zimoun
2020-06-19 10:00 ` zimoun
2020-06-19 12:16 ` elaexuotee
2020-06-19 20:40 ` Ludovic Courtès
2020-06-19 20:35 ` Ludovic Courtès
2020-06-16 2:51 ` Using --manfistest with <profile>/manifest files George Clemmer
2020-06-16 4:27 ` elaexuotee
2020-06-17 19:09 ` George Clemmer
2020-06-16 9:38 ` zimoun
2020-06-16 14:03 ` George Clemmer
2020-06-16 15:09 ` zimoun
2020-06-16 9:50 ` Ludovic Courtès
2020-06-15 7:54 ` zimoun
2020-06-15 10:08 ` elaexuotee
2020-06-16 9:09 ` zimoun [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=86eeqfs7fm.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=elaexuotee@wilsonb.com \
--cc=guix-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).