On 10/13/2017 05:56 PM, Mark Hatle wrote:
On 10/13/17 9:18 AM, Alexander Kanavin wrote:
Instead of reporting that we can update to a bogus version
report that upstream version is not known.
You do know that there are release branches for prelink right?
http://git.yoctoproject.org/cgit/cgit.cgi/prelink-cross/refs/heads
cross_prelink and master are both 'release' quality branches.
Anything put there is a new version.
There is nothing for us to 'tag', since there are no formal versions.
Should be easy enough for the system to compare the SRCREV to the top of
cross_prelink. If they don't match, an upgrade is needed.
The system currently supports only comparing tags, not comparing
commits. I've filed a bug for it long time ago:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=8133
and no progress happened. In the meantime, for projects where commit ==
release, the best we can do is to mark them as 'upstream version cannot
be established'. For prelink, also an exclusion of a bogus tag is
needed, so you, as the maintainer, won't get reminders to update to it.
Alex
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
