From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Giovanni Biscuolo <g@xelera.eu>,
znavko@disroot.org, help-guix <help-guix@gnu.org>
Subject: Re: Why reproducibility is breaking by metadata?
Date: Mon, 08 Jul 2019 09:51:33 +0200 [thread overview]
Message-ID: <m1pnmlvu9m.fsf@ordinateur-de-catherine--konrad.home> (raw)
In-Reply-To: <87k1cvxzga.fsf@roquette.mug.biscuolo.net>
Hi Giovanni,
> Just "food for thought": git-annex metadata allows users to attach
> arbitrary metadata to their annexed files, «metadata is stored in the
> git-annex branch, and so is automatically kept in sync with the rest of
> git-annex's state»
That's indeed a nice example of how to handle metadata in a better way.
But it does require more than a plain files, so publishing and archiving
the metadata requires additional tools (git in this case).
> I doubt this could be applied to `guix pack`, but it's an intereting
> approach to "sidecar" metadata
We could adapt the idea to the Guix store. Write the metadata to a
separate file in the store that has the same filename as the packed
archive, but an additional extension. Since the filename contains the
hash of the archive contents, the relation between data and metadata
is also maintained.
Konrad.
prev parent reply other threads:[~2019-07-08 7:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 4:05 Why reproducibility is breaking by metadata? znavko
2019-07-03 6:13 ` Julien Lepiller
2019-07-03 6:39 ` Konrad Hinsen
2019-07-06 9:52 ` Giovanni Biscuolo
2019-07-08 7:51 ` Konrad Hinsen [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=m1pnmlvu9m.fsf@ordinateur-de-catherine--konrad.home \
--to=konrad.hinsen@fastmail.net \
--cc=g@xelera.eu \
--cc=help-guix@gnu.org \
--cc=znavko@disroot.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.
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).