From: "Ludovic Courtès" <ludo@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Store channel specification in profile
Date: Tue, 11 Feb 2020 15:10:13 +0100 [thread overview]
Message-ID: <87zhdp2p16.fsf@gnu.org> (raw)
In-Reply-To: <8736bldmzr.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Sat, 08 Feb 2020 18:09:44 +0100")
Howdy!
Pierre Neidhardt <mail@ambrevar.xyz> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
[...]
>> I would, however, use sexps as a serialization format. Compared to an
>> API, an object serialized to an sexp has the advantage that we can write
>> code to handle changes in the serialization format, so it’s future-proof
>> if we get it right. But then: we’re back to ‘manifest’. :-)
>>
>> I hope this is a bit clearer, but I realize it’s tricky to discuss such
>> things!
>
> Indeed, because we were on the same page all along: my "keyed code snippet"
> was about the serialization format, not the data structure!
Good.
>> ‘manifest’ looks like this:
>>
>> (manifest
>> (version 3)
>> …)
>>
>> We have an explicit ‘read-manifest’ procedure that can handle version 3,
>> but also prior versions, and this is all transparent.
>>
>> You cannot do that with code. Code is just evaluated, and if it’s
>> incompatible, if fails in some unspecified way.
>
> Same thing, what I had in mind was to store the version number in the
> _serialized_ specifications.scm, as for the manifest.
>
> This way I believe we can support multiple version for specifications.scm.
> Am I missing something?
Then I don’t get how ‘specifications.scm’ would differ from ‘manifest’.
In both cases we’re talking about a serialization format containing
per-package provenance info, right?
>> We could store package transformations as manifest entry properties.
>>
>> However, that’ll be an approximation: the exact implementation of
>> ‘--with-input’, for instance, can vary over time.
>
> Hmmm, even if we have the provenance?
Yes.
>> After all, the goal of the functionality we’re discussing is to allow
>> users to move towards the declarative ‘manifest.scm’ style, right?
>
> Yes, so I'll try to sum up what I want to achieve in one sentence:
> "automate the textual serialization of profile specifications to
> simplify their backup/deployment/reproduction".
OK.
To me, serialization is already automated: it’s the ‘manifest’ file.
What we lack is the ability to obtain a “manifest.scm” kind of file
(code) that users can pick as a starting point in their migration
towards declarative deployment.
Does that make sense? Am I paraphrasing you correctly? :-)
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-02-11 14:10 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 14:55 Store channel specification in profile Pierre Neidhardt
2019-11-26 16:40 ` Konrad Hinsen
2019-11-26 19:12 ` Pierre Neidhardt
2019-11-26 19:35 ` Konrad Hinsen
2019-12-02 15:58 ` zimoun
2019-12-09 17:11 ` Ludovic Courtès
2019-12-09 17:21 ` Pierre Neidhardt
2019-12-12 19:50 ` zimoun
2019-12-12 22:35 ` Pierre Neidhardt
2019-12-13 12:16 ` zimoun
2019-12-19 16:12 ` Ludovic Courtès
2019-12-19 17:18 ` zimoun
2020-01-06 20:07 ` Pierre Neidhardt
2020-01-06 21:09 ` zimoun
2020-01-08 15:17 ` Pierre Neidhardt
2020-01-08 19:31 ` zimoun
2020-01-11 23:48 ` Ludovic Courtès
2020-01-13 14:02 ` Pierre Neidhardt
2020-01-13 14:46 ` zimoun
2020-01-13 14:37 ` zimoun
2020-01-13 14:59 ` Pierre Neidhardt
2020-01-13 15:53 ` zimoun
2020-01-13 16:53 ` Pierre Neidhardt
2020-01-30 19:24 ` Pierre Neidhardt
2020-01-31 8:51 ` zimoun
2020-01-31 9:21 ` Konrad Hinsen
2020-01-31 11:21 ` Pierre Neidhardt
2020-01-31 12:15 ` Pierre Neidhardt
2020-01-31 16:01 ` Konrad Hinsen
2020-02-05 11:08 ` Ludovic Courtès
2020-02-06 10:59 ` Pierre Neidhardt
2020-02-07 21:28 ` Ludovic Courtès
2020-02-08 17:09 ` Pierre Neidhardt
2020-02-11 14:10 ` Ludovic Courtès [this message]
2020-02-11 14:18 ` Pierre Neidhardt
2020-02-24 16:16 ` Ludovic Courtès
2020-02-25 10:32 ` Pierre Neidhardt
2020-03-03 21:43 ` zimoun
2020-03-04 8:09 ` Pierre Neidhardt
2020-03-04 13:24 ` zimoun
2020-03-03 21:49 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zhdp2p16.fsf@gnu.org \
--to=ludo@gnu.org \
--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 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.