From: Giovanni Biscuolo <g@xelera.eu>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>,
znavko@disroot.org, help-guix <help-guix@gnu.org>
Subject: Re: Why reproducibility is breaking by metadata?
Date: Sat, 06 Jul 2019 11:52:05 +0200 [thread overview]
Message-ID: <87k1cvxzga.fsf@roquette.mug.biscuolo.net> (raw)
In-Reply-To: <m1v9wjd3kr.fsf@ordinateur-de-catherine--konrad.home>
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
Hello Konrad,
Konrad Hinsen <konrad.hinsen@fastmail.net> writes:
[...]
> Philosophical side note: the right way to store provenance information
> is outside of the data they refer to. Unfortunately, with file-based
> storage, there is no clean way to attach the provenance information
> securely to the data without putting it into the same file.
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»
Being content-hashed, each file will persintently keep its metadata even
in case of renames (in the git-annex "filesystem" scope)
I doubt this could be applied to `guix pack`, but it's an intereting
approach to "sidecar" metadata
Happy Guix! Gio'.
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-07-06 9:52 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 [this message]
2019-07-08 7:51 ` Konrad Hinsen
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=87k1cvxzga.fsf@roquette.mug.biscuolo.net \
--to=g@xelera.eu \
--cc=help-guix@gnu.org \
--cc=konrad.hinsen@fastmail.net \
--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).