On Thu, 14 May 2020 at 22:59, Diego Rondini <diego.rond...@kynetics.com> wrote:
> Hi Alexander, > > On Thu, May 14, 2020 at 7:31 PM Alexander Kanavin <alex.kana...@gmail.com> > wrote: > >> You can't generally update to a random development commit, especially if >> PV stays the same. Please ask upstream to make a new release. >> >> > Thank you for your feedback, I understand your point. > The odd thing is that the situation is already broken, as what's in > oe-core master right now is not bmap-tools release 3.5, but some "random > development commit" in between 3.5 and current master: > > http://git.openembedded.org/openembedded-core/commit/meta/recipes-support/bmap-tools?id=3fbee26af2f3263180f75652b5dd6e50adb1d8fe > > https://github.com/intel/bmap-tools/commits/master > Release 3.5: > > https://github.com/intel/bmap-tools/commit/14b411a65c371e273fe599bee9e52bd9f9b751e1 > Commit in oe-core: > > https://github.com/intel/bmap-tools/commit/db7087b883bf52cbff063ad17a41cc1cbb85104d > > What do you suggest? > Right - generally we need to trust that version updates don't do this, and there's no easy way to detect this. The recipe already does: PV .= "+git${SRCPV}" which is the standard way to mark "random development commits", so I'd say resubmit your patch with an explanation in the commit log that you're merely bumping one development snapshot to a newer development snapshot.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#138300): https://lists.openembedded.org/g/openembedded-core/message/138300 Mute This Topic: https://lists.openembedded.org/mt/74205770/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
