From: <znavko@tutanota.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Software Heritage & Guix
Date: Sun, 31 Mar 2019 08:27:39 +0200 (CEST) [thread overview]
Message-ID: <LbHQdrG--3-1@tutanota.com> (raw)
In-Reply-To: <87wokh8y4p.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
Hello! Looks like reproducible builds are like videos on video hosting. You may share your screencast or videos, the others can see your screen exactly. But there are limitations: you need to have an account on exactly one video hosting. There were challenges in Ludovic Courtès article. Releases tarballs are not the same as version control revisions: tarballs may have `configure` scripts and developers signatures. What to choose for using in certain reproducible build?
There is in need a help from FSF for definition of standards. What do you think?
Mar 29, 2019, 4:05 PM by ludo@gnu.org:
> Hello!
>
> I’ve written a post on the Software Heritage support in Guix:
>
> > https://gnu.org/s/guix/blog/2019/connecting-reproducible-deployment-to-a-long-term-source-code-archive <https://gnu.org/s/guix/blog/2019/connecting-reproducible-deployment-to-a-long-term-source-code-archive/>
>
> Happy reading! :-)
>
> Ludo’.
>
[-- Attachment #2: Type: text/html, Size: 1945 bytes --]
next prev parent reply other threads:[~2019-03-31 6:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 16:05 Software Heritage & Guix Ludovic Courtès
2019-03-29 16:42 ` John Soo
2019-03-29 18:19 ` sirgazil
2019-03-30 13:46 ` Pjotr Prins
2019-03-30 15:51 ` znavko
2019-03-30 17:30 ` Pjotr Prins
2019-03-30 18:03 ` znavko
2019-03-30 19:13 ` swedebugia
2019-03-31 16:24 ` Ludovic Courtès
2019-03-31 16:22 ` Ludovic Courtès
2019-03-31 1:57 ` mikadoZero
2019-03-31 16:30 ` Ludovic Courtès
2019-04-03 0:58 ` mikadoZero
2019-04-03 8:17 ` Giovanni Biscuolo
2019-04-03 21:27 ` Ludovic Courtès
2019-03-31 6:27 ` znavko [this message]
2019-04-01 8:33 ` znavko
2019-04-03 7:57 ` Chris Marusich
2019-04-18 16:39 ` Ludovic Courtès
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=LbHQdrG--3-1@tutanota.com \
--to=znavko@tutanota.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
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.