From: Leif Lindholm <leif.lindholm@linaro.org>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [RFC] Proposal to add edk2-apps repository
Date: Thu, 29 Nov 2018 22:41:02 +0000 [thread overview]
Message-ID: <20181129224102.ab43kwgrkk6xz2bl@bivouac.eciton.net> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5B8B381E8@ORSMSX113.amr.corp.intel.com>
On Thu, Nov 29, 2018 at 05:58:08PM +0000, Kinney, Michael D wrote:
> Hello,
>
> I would like to propose the creation of a new
> repository called edk2-apps. This repository
> would initially be used to host the following
> packages from the edk2 repository:
>
> * AppPkg
> * StdLib
> * StdLibPrivateInternalFiles
Let me start by saying I 100% back moving these out of the main edk2
repository.
> These 3 packages provide support for the libc along
> with applications that depend on libc. None of the
> other packages in the edk2 repository use these
> packages, so these 3 package can be safely moved
> without any impacts to platform firmware builds.
> Build configurations that do use libc features can
> clone the edk2-apps repository and add it to
> PACKAGES_PATH.
I must confess to never having properly understood the scope of AppPkg
to begin with.
AppPkg/Applications/Hello does not appear to have any further (real)
dependency on libc than MdeModulePkg/Application/HelloWorld/, and .
And certainly MdeModulePkg/Applications contain plenty of
... applications.
So, if the purpose is simply to provide some examples of application
written to libc rather than UEFI - should this be edk2-libc instead?
Best Regards,
Leif
> The history of these 3 packages would be preserved
> when importing the content into edk2-apps. After
> The import is verified, these 3 packages would be
> deleted from the edk2 repository.
>
> This proposal helps reduce the size of the edk2
> repository and focuses edk2 repository on packages
> used to provide UEFI/PI conformant firmware.
>
> If there are no concerns with this proposal, I will
> enter a Tianocore BZs for the two steps.
>
> Best regards,
>
> Mike
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2018-11-29 22:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 17:58 [RFC] Proposal to add edk2-apps repository Kinney, Michael D
2018-11-29 22:41 ` Leif Lindholm [this message]
2018-11-30 0:46 ` Kinney, Michael D
2018-11-30 1:44 ` krishnaLee
2018-11-30 3:40 ` Ni, Ruiyu
2018-11-30 15:49 ` Carsey, Jaben
2018-11-30 16:48 ` Kinney, Michael D
2018-12-03 2:01 ` krishnaLee
2018-11-30 6:03 ` Andrew Fish
2018-12-03 14:11 ` Laszlo Ersek
2018-12-03 15:07 ` Leif Lindholm
2018-12-03 17:10 ` Laszlo Ersek
2018-12-11 7:26 ` David F.
2018-11-30 3:32 ` Ni, Ruiyu
2018-11-30 4:57 ` Kinney, Michael D
2018-12-03 14:21 ` Laszlo Ersek
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=20181129224102.ab43kwgrkk6xz2bl@bivouac.eciton.net \
--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