Re: [edk2-devel] EDK II Stable Tag release edk2-stable201905 completed

["Laszlo Ersek" <lersek@redhat.com>]

On 06/10/19 16:00, Leif Lindholm wrote:
> On Mon, Jun 10, 2019 at 01:50:43PM +0000, Gao, Liming wrote:
>> edk2 submodule are from github openssl and berkeley-softfloat-3. If you can access edk2, you can also access them. Why you system redirect github openssl to boringssl?
>>
>> * [CryptoPkg/Library/OpensslLib/openssl](https://github.com/openssl/openssl/blob/50eaac9f3337667259de725451f201e784599687/LICENSE)
>> * [ArmPkg/Library/ArmSoftFloatLib/berkeley-softfloat-3](https://github.com/ucb-bar/berkeley-softfloat-3/blob/b64af41c3276f97f0e181920400ee056b9c88037/COPYING.txt)
> 
> Argh, no. OpenSSL has boringssl as a git submodule.
> 
> edk2/CryptoPkg/Library/OpensslLib/openssl$ cat .gitmodules
> [submodule "boringssl"]
>         path = boringssl
>         url = https://boringssl.googlesource.com/boringssl
> ...
> 

That's right, but it shouldn't matter. In edk2, I always use

$ git submodule update --init --force

and I never pass the "--recursive" flag. This is also how I tested the
upgrade to OpenSSL-1.1.1b, before edk2-stable201905 was tagged. The
boringssl sub-sub-module is not needed for edk2's purposes.

We might want to drop "--recursive" from "OpenSSL-HOWTO.txt", instead.

Thanks
Laszlo