From: Paolo Bonzini <pbonzini@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>
Cc: "Stefan Weil" <sw@weilnetz.de>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Rainer M?ller" <raimue@macports.org>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [qemu-web PATCH] download: Add instructions for MacPorts
Date: Wed, 4 Apr 2018 19:23:47 +0200 [thread overview]
Message-ID: <5f03cc19-de3a-b599-dfc1-405f6fef4f9c@redhat.com> (raw)
In-Reply-To: <0B844F19-6C50-475D-B33D-3A66620A2595@gmail.com>
On 04/04/2018 18:19, Programmingkid wrote:
>>> I guess there is just too much distrust to provide a QEMU binary for download.
>> It's not distrust, it's responsibility.
>>
>> Paolo
> So from what I learned, in order to provide a binary of QEMU, these things must be done:
> - Some kind of checksum be provided for the binary (md5, SHA512, ...)
> - A zip file that has the exact code used to build the binary be provided
> - The complete environment use to build the binary be documented
> -- Operating system name and version
> -- name and version of various tools used to build the binary (GCC, make, ...)
> -- name and version of libraries that are linked to QEMU (libc, pixman, ...)
> - The exact command-line options used to build the binary be provided
> - The email address and identity of the person who made the binary be provided
>
> If anything is missing please feel free to share.
In practice a GPG signature, with a signature well-connected to other
people in the QEMU community, would already be a very good start. If
the exact code is not a release tarball, that would also be required.
The command line options used for the build can be documented in the wiki.
Paolo
next prev parent reply other threads:[~2018-04-04 17:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.35816.1522678020.27992.qemu-devel@nongnu.org>
2018-04-02 14:13 ` [Qemu-devel] [qemu-web PATCH] download: Add instructions for MacPorts Programmingkid
2018-04-04 11:15 ` Paolo Bonzini
2018-04-04 14:24 ` Programmingkid
2018-04-04 14:38 ` Daniel P. Berrangé
2018-04-04 14:45 ` Paolo Bonzini
2018-04-04 14:58 ` Daniel P. Berrangé
2018-04-04 15:55 ` Stefan Weil
2018-04-04 16:05 ` Programmingkid
2018-04-04 16:08 ` Paolo Bonzini
2018-04-04 16:19 ` Programmingkid
2018-04-04 17:23 ` Paolo Bonzini [this message]
2018-04-04 16:11 ` Paolo Bonzini
2018-04-04 17:41 ` Stefan Weil
2018-04-05 5:56 ` Paolo Bonzini
2018-04-01 16:22 Rainer Müller
2018-04-02 2:22 ` Paolo Bonzini
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=5f03cc19-de3a-b599-dfc1-405f6fef4f9c@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=programmingkidx@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=raimue@macports.org \
--cc=sw@weilnetz.de \
/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 NNTP newsgroup(s).