From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org, elaexuotee@wilsonb.com
Subject: Re: Using --manfistest with <profile>/manifest files
Date: Tue, 16 Jun 2020 11:46:34 +0200 [thread overview]
Message-ID: <871rmfwdfp.fsf@gnu.org> (raw)
In-Reply-To: <86lfko92fj.fsf@gmail.com> (zimoun's message of "Mon, 15 Jun 2020 10:08:16 +0200")
Hi,
zimoun <zimon.toutoune@gmail.com> skribis:
> On Sun, 14 Jun 2020 at 17:24, Ludovic Courtès <ludo@gnu.org> wrote:
>
>> I think there were several issues we discussed:
>>
>> 1. We can only approximate that actual profile content; storing
>> an approximate ‘manifest.scm’ along with the profile would IMO be
>> deceptive.
>>
>> 2. It’s easy to maintain compatibility over a data format, but it’s
>> much harder to maintain compatibility for code.
>>
>> I think we discussed these issues the best we could in the megathread,
>> so I’m personally in favor of moving forward in a pragmatic way.
>
> By pragmatic way, you mean:
>
> - let the format of <profile>/manifest as it is,
> - write '--export-manifest' as an approximation
>
> right?
For example, yes.
> Well, I personally changed my workflow and now I always use manifest
> files. And the situation that I described in the manifest about the
> "Working Scientific" doing install, pull, install, pull, remove,
> install, etc. is rooted in bad practises, so it should be avoided.
>
> Therefore, I agree that '--export-manifest' is the right approach, as an
> helping tool; too bad for some corner cases. :-)
Yeah, I think our goal is just to provide a tool to migrate from the
“imperative” way to the declarative way. Once people have gotten
started with manifests, they no longer need that migration tool.
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-06-16 9:48 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 [this message]
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
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=871rmfwdfp.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=elaexuotee@wilsonb.com \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.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 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).