On Wed, Mar 27, 2019 at 04:03:27PM +0200, Adrian Bunk wrote: > On Wed, Mar 27, 2019 at 02:33:14PM +0100, Martin Jansa wrote: > > On Tue, Mar 26, 2019 at 12:42:12PM +0200, Adrian Bunk wrote: > >... > > > Not having the release there also loses the ability to use either > > > gcc_%.bbappend or gcc_8.3.0.bbappend, which are suitable for > > > different situations. > > > > There is usually just one version per recipe and even with _git.bb > > suffix you can easily do gcc_7+git.bb and gcc_8+git.bb if you need to. > > Thud contains 8.2 today, but might have 8.3 tomorrow. > > A layer might want to append only to one of them, > or have different appends for different versions. > > That's trivial with gcc_8.2.bb and gcc_8.3.bb, > and harder with gcc_8+svn.bb.
If your layer has gcc_8.2.bbappend and the recipe in oe-core gets renamed from gcc_8.2.bb to gcc_8.3.bb in newer thud revision, then your bbappend will not apply and bitbake will complain that there is no recipe for your gcc_8.2.bbappend. Layer which doesn't even parse correctly with different revisions of the same thud branch isn't really something we should encourage. gcc_8%.bbappend with some logic inside (e.g. adding some .patch file only when PV starts with 8.2) will be compatible with both newer and older revision of thud. -- Martin 'JaMa' Jansa jabber: [email protected]
signature.asc
Description: Digital signature
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
