Re: [edk2] [RFC] Plan to delete ShellBinPkg from edk2/master

["Michael D Kinney" <michael.d.kinney@intel.com>]

Laszlo,

A PREBUILD action looks like a good idea.

Release artifacts in GitHub are available as an http
link, so a python script to download into a path
in the build output directory and referenced by DSC/FDF
should work.

We could even post shell binaries for the past couple
edk2-stable tags because release content can be updated.

Mike

> -----Original Message-----
> From: Laszlo Ersek [mailto:lersek@redhat.com]
> Sent: Wednesday, April 3, 2019 9:07 AM
> 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
> Cc: Cetola, Stephano <stephano.cetola@intel.com>; Gao,
> Liming <liming.gao@intel.com>; Carsey, Jaben
> <jaben.carsey@intel.com>
> Subject: Re: [edk2] [RFC] Plan to delete ShellBinPkg
> from edk2/master
> 
> 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