From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <lersek@redhat.com>
Received-SPF: Pass (sender SPF authorized) identity=mailfrom;
 client-ip=209.132.183.28; helo=mx1.redhat.com; envelope-from=lersek@redhat.com;
 receiver=edk2-devel@lists.01.org 
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by ml01.01.org (Postfix) with ESMTPS id D4B322194EB70
 for <edk2-devel@lists.01.org>; Wed,  3 Apr 2019 09:07:15 -0700 (PDT)
Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com
 [10.5.11.16])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.redhat.com (Postfix) with ESMTPS id 6A525461CF;
 Wed,  3 Apr 2019 16:07:09 +0000 (UTC)
Received: from lacos-laptop-7.usersys.redhat.com (ovpn-120-127.rdu2.redhat.com
 [10.10.120.127])
 by smtp.corp.redhat.com (Postfix) with ESMTP id C51D05C553;
 Wed,  3 Apr 2019 16:07:07 +0000 (UTC)
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
 "Ni, Ray" <ray.ni@intel.com>, "Bi, Dandan" <dandan.bi@intel.com>,
 "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Cetola, Stephano" <stephano.cetola@intel.com>,
 "Gao, Liming" <liming.gao@intel.com>, "Carsey, Jaben"
 <jaben.carsey@intel.com>
References: <3C0D5C461C9E904E8F62152F6274C0BB40BB5D6F@SHSMSX104.ccr.corp.intel.com>
 <9492a5a0-58fc-4e49-4645-0593aa758660@redhat.com>
 <734D49CCEBEEF84792F5B80ED585239D5C0C69A2@SHSMSX104.ccr.corp.intel.com>
 <82ac9c41-e12d-7287-74f2-d8bea4516280@redhat.com>
 <E92EE9817A31E24EB0585FDF735412F5B9C774C3@ORSMSX112.amr.corp.intel.com>
From: Laszlo Ersek <lersek@redhat.com>
Message-ID: <565232dc-a0ff-7b1b-3a7c-9c6db0b26969@redhat.com>
Date: Wed, 3 Apr 2019 18:07:04 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5B9C774C3@ORSMSX112.amr.corp.intel.com>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16
 (mx1.redhat.com [10.5.110.29]); Wed, 03 Apr 2019 16:07:09 +0000 (UTC)
Subject: Re: [RFC] Plan to delete ShellBinPkg from edk2/master
X-BeenThere: edk2-devel@lists.01.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: EDK II Development  <edk2-devel.lists.01.org>
List-Unsubscribe: <https://lists.01.org/mailman/options/edk2-devel>,
 <mailto:edk2-devel-request@lists.01.org?subject=unsubscribe>
List-Archive: <http://lists.01.org/pipermail/edk2-devel/>
List-Post: <mailto:edk2-devel@lists.01.org>
List-Help: <mailto:edk2-devel-request@lists.01.org?subject=help>
List-Subscribe: <https://lists.01.org/mailman/listinfo/edk2-devel>,
 <mailto:edk2-devel-request@lists.01.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2019 16:07:16 -0000
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit

On 04/03/19 17:49, Kinney, Michael D wrote:
> Laszlo,
> 
> I think it makes sense to post validated shell binaries
> with the edk2-stable tag releases.  GitHub does support
> this when a release tag is made.
> 
> However, we would need to make it simple for a platform
> to use a binary from that location.  We may need some
> enhancements to pull in binary artifacts from different
> locations to support a platform build that uses one or
> more pre-built binaries.

Can PREBUILD scripts (written by platform owners) download the required
binaries?

Thanks,
Laszlo