On 9 May 2017 at 03:44, Manjukumar Harthikote Matha <[email protected]> wrote: > > >> -----Original Message----- >> From: [email protected] [mailto:meta-xilinx- >> [email protected]] On Behalf Of Nathan Rossi >> Sent: Sunday, May 07, 2017 7:07 AM >> To: [email protected] >> Subject: [meta-xilinx] [PATCH 9/12] arm-trusted-firmware_2016.3.bb: Rename >> the >> _git.bb to the actual release >> >> Rename the arm-trusted-firmware recipe so that the filename matches the >> release >> version of the recipe. >> > > Hi Nathan, > > I don't think it is good to deviate from upstream naming convention. Yocto > OE-core prefers using versions or _git not release versions (specially > 2016.4, 2017.1 etc). We should not deviate from this methodology
This is a deviation towards upstream naming/versioning convention. In this case upstream being Xilinx's vendor tree. This is also making atf follow the same convention used by other Xilinx release versioned recipes in meta-xilinx. This change is also to handle the dual recipe versions (2016.3 and 2017.1), which would be broken if using "_git". And "_git.bb" is normally used for recipes that point at unreleased/non-final git srcrev's. It should not be used in this case as the recipes point at specific known releases (Xilinx ones). Whilst this recipe started out as a _git due to pointing to an unreleased Xilinx tree, it was never updated to use its PV. If you dislike the recipe filenames having just the Xilinx release version, a more complete PV (aka. 1.2-xilinx-v2016.3) could be used but that just seems unnecessary. Regards, Nathan -- _______________________________________________ meta-xilinx mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-xilinx
