From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=134.134.136.126; helo=mga18.intel.com; envelope-from=michael.d.kinney@intel.com; receiver=edk2-devel@lists.01.org Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) (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 DB1D9211B8182 for ; Wed, 16 Jan 2019 10:57:32 -0800 (PST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Jan 2019 10:57:32 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,487,1539673200"; d="scan'208,217";a="312374944" Received: from orsmsx109.amr.corp.intel.com ([10.22.240.7]) by fmsmga005.fm.intel.com with ESMTP; 16 Jan 2019 10:57:31 -0800 Received: from orsmsx161.amr.corp.intel.com (10.22.240.84) by ORSMSX109.amr.corp.intel.com (10.22.240.7) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 16 Jan 2019 10:57:31 -0800 Received: from orsmsx113.amr.corp.intel.com ([169.254.9.240]) by ORSMSX161.amr.corp.intel.com ([169.254.4.192]) with mapi id 14.03.0415.000; Wed, 16 Jan 2019 10:57:31 -0800 From: "Kinney, Michael D" To: "edk2-devel@lists.01.org" , "Kinney, Michael D" Thread-Topic: [RFC v2] Proposal to add edk2-libc Thread-Index: AdSty8KsBNPyeoO2S3eWIsYip1LR6g== Date: Wed, 16 Jan 2019 18:57:30 +0000 Message-ID: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [10.22.254.140] MIME-Version: 1.0 X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: [RFC v2] Proposal to add edk2-libc X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jan 2019 18:57:33 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello, I shared an RFC in November to add an edk2-apps repository. https://lists.01.org/pipermail/edk2-devel/2018-November/033330.html Feedback in this thread discussed that there are three types of applications. Apps that use libc, UEFI Shell apps, and UEFI Applications. I would like this RFC to focus on libc applications, and changes related to UEFI Shell apps and UEFI Applications can be handled separately. The updated RFC is shown below. The repo name has been changed from edk2-apps to edk2-libc based on feedback from Leif. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D I would like to propose the creation of a new repository called edk2-libc. This repository would initially be used to host the following packages from the edk2 repository: * AppPkg * StdLib * StdLibPrivateInternalFiles 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-libc repository and add it to PACKAGES_PATH. The history of these 3 packages would be preserved when importing the content into edk2-libc. 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