From: "Ludovic Courtès" <ludo@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org, elaexuotee@wilsonb.com
Subject: Re: Using --manfistest with <profile>/manifest files
Date: Tue, 16 Jun 2020 11:44:54 +0200 [thread overview]
Message-ID: <875zbrwdih.fsf@gnu.org> (raw)
In-Reply-To: <87d060epfj.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Mon, 15 Jun 2020 09:52:32 +0200")
Hi Pierre,
Pierre Neidhardt <mail@ambrevar.xyz> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> I think there were several issues we discussed:
>
> Allow me to reiterate, at the risk of bikeshedding... :)
>
>> 1. We can only approximate that actual profile content; storing
>> an approximate ‘manifest.scm’ along with the profile would IMO be
>> deceptive.
>
> Why is an approximate file more of a problem than a command producing
> an approximate result? We could include a warning comment at the top of
> the file to make it explicit that it's approximate.
>
>> 2. It’s easy to maintain compatibility over a data format, but it’s
>> much harder to maintain compatibility for code.
>
> I'm confused: my suggestion is to add a new data format, so isn't it
> better then?
We seem to be talking past each other. IMO, exporting a file is easily
done and better than nothing. I think we should be pragmatic.
If you want, maybe you can prototype something that we could discuss?
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-06-16 9:45 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 [this message]
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
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=875zbrwdih.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=elaexuotee@wilsonb.com \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/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).