About PV = "0.0+git${SRCPV}"
There are several recipes in oe-core which has:
PV = "0.0+git${SRCPV}"
These recipes don't have a release version, so we use "0.0+git${SRCPV}", but the package manager such as opkg/rpm/smart may not upgrade them correctly when the recipes is upgraded since we can't make sure that SRCPV_new > SRCPV_old.
How about we use date for these recipes which doesn't have a release version? For example, if we integrate them to oe-core today, then PV = "20160421". And when we upgrade them in the future, we can change the PV to that day. We can change all the current version 0.0 target recipes to today, and add a sanity check for version 0.0.
Signature · 3 lines
Thanks Robert
Quoted 9 lines · Robert Yang
There are several recipes in oe-core which has:
PV = "0.0+git${SRCPV}"These recipes don't have a release version, so we use "0.0+git${SRCPV}",
but the package manager such as opkg/rpm/smart may not upgrade them correctly when the recipes is upgraded since we can't make sure thatSRCPV_new>SRCPV_old.
Quoted 6 lines
How about we use date for these recipes which doesn't have a release version? For example, if we integrate them to oe-core today, then PV = "20160421". And when we upgrade them in the future, we can change
the PV to that day. We can change all the current version 0.0 target recipes to today, and add a sanity check for version 0.0.
No, this is the whole idea behind having the PR Server which injects a revision before the hash in SRCPV. We have the same problem with other git recipes even where there are versions since the revision can change and we need to be able to sort the versions correctly.
Cheers,
Richard
Quoted 17 lines · Richard Purdie
Quoted 9 lines · Robert Yang
There are several recipes in oe-core which has:
PV = "0.0+git${SRCPV}"These recipes don't have a release version, so we use "0.0+git${SRCPV}",
but the package manager such as opkg/rpm/smart may not upgrade them correctly when the recipes is upgraded since we can't make sure thatSRCPV_new>SRCPV_old.Quoted 6 lines
How about we use date for these recipes which doesn't have a release version? For example, if we integrate them to oe-core today, then PV = "20160421". And when we upgrade them in the future, we can change
the PV to that day. We can change all the current version 0.0 target recipes to today, and add a sanity check for version 0.0.
Quoted 4 lines
No, this is the whole idea behind having the PR Server which injects a revision before the hash in SRCPV. We have the same problem with other git recipes even where there are versions since the revision can change and we need to be able to sort the versions correctly.
Thanks, I saw that PR Server will change git0 -> git1 -> git2 when SRCREV is changed, it works.
// Robert
Quoted 5 lines
Cheers,
Richard