On Sun, May 17, 2020 at 3:22 PM Adrian Bunk <b...@stusta.de> wrote: > > That I believe would be a terrible mistake when people opt-in to take > > a layer, but never care about updating it... :( > > The typical Yocto user starts with whatever prehistoric Yocto release > came with the BSP distribution for the reference hardware, and then > develops a new product on top of that. > > I would not be surprised if someone will have the initial Yocto 2.7 > release, but uses the latest from the corresponding meta-openembedded > branch on top. >
And should these people really block us doing changes which require update in multiple layers at "the same time"? If they are using the prehistory revision of given Yocto release and not even the latest revision in given branch, then they are already missing much more than 3 python recipes migrated from meta-oe and they should learn to update the layers they are using, I think we have relatively good track of not breaking stable branches with incompatible changes, so upgrading from e.g. initial release revision of dunfell to latest in oe-core together with all other layers, shouldn't cause (m)any issues after 5 years when someone will be looking at this BSP which got released with prehistory dunfell release. Point releases are nice, but people should really use whatever is latest revisions in the branches they use and that's IMHO the recommendation from Yocto Project itself as well (IIRC we discussed it in OE TSC when talking about tags for point releases). Regards,
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#138378): https://lists.openembedded.org/g/openembedded-core/message/138378 Mute This Topic: https://lists.openembedded.org/mt/74214757/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
