From: Laszlo Ersek <lersek@redhat.com>
To: Tim Lewis <tim.lewis@insyde.com>,
"'Bjorge, Erik C'" <erik.c.bjorge@intel.com>,
edk2-devel@lists.01.org
Subject: Re: RFC: Proposal to halt automatic builds of Windows BaseTools executables
Date: Thu, 8 Mar 2018 22:18:35 +0100 [thread overview]
Message-ID: <2936c498-170d-84b8-4b1b-e103c463eefd@redhat.com> (raw)
In-Reply-To: <00ef01d3b708$059e05e0$10da11a0$@insyde.com>
On 03/08/18 19:05, Tim Lewis wrote:
> Erik --
>
> What is the justification? Moving from more immediately usable to less
> immediately usable doesn't seem, on the surface, to be a good direction.
> Why not go the other direction and pre-build the binaries for the other
> environments?
I'd just like to offer one data point for the last question: most open
source developers *really* dislike running any native binaries that were
built by neither (a) themselves nor (b) the provider of their OS
distribution.
To give you an example for (b), Fedora provides the "edk2-tools" package
(built from the "edk2" source package), and "edk2-tools" definitely
installs native binaries:
https://koji.fedoraproject.org/koji/rpminfo?rpmID=13354362
The difference is that these binaries were built in a build environment
that matches the rest of Fedora [*] and is generally trusted by Fedora
users.
[*] For example, binaries could be instrumented for security purposes
system-wide; some buffer overflows in a native (C) application could be
caught automatically as a result.
Thanks,
Laszlo
next prev parent reply other threads:[~2018-03-08 21:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 17:56 RFC: Proposal to halt automatic builds of Windows BaseTools executables Bjorge, Erik C
2018-03-08 1:21 ` Gao, Liming
2018-03-08 18:05 ` Tim Lewis
2018-03-08 18:37 ` Andrew Fish
2018-03-08 19:52 ` Bjorge, Erik C
2018-03-08 21:18 ` Laszlo Ersek [this message]
2018-03-08 21:36 ` Tim Lewis
2018-03-08 22:19 ` Andrew Fish
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-list 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=2936c498-170d-84b8-4b1b-e103c463eefd@redhat.com \
--to=devel@edk2.groups.io \
/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