<div dir="ltr">See:<div><a href="https://bugzilla.yoctoproject.org/show_bug.cgi?id=5970">https://bugzilla.yoctoproject.org/show_bug.cgi?id=5970</a><br></div><div><br></div><div>Just using recipe checksum wont work, because the main reason for PR bumps is to automatically upgrade the packages when one of the dependencies changes .so version, which you won't detect from recipe checksum of the app which is just using the library.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 18, 2016 at 8:09 AM, Robert Yang <span dir="ltr"><<a href="mailto:liezhi.yang@windriver.com" target="_blank">liezhi.yang@windriver.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The PRServer bumps PR according to do_package's task hash, that<br>
causes it bumps *all* packages' PR when recipes like pseudo-native<br>
and rpm-native is changed. It is a very bad user experience when we<br>
run "smart/opkg upgrade" on running target, for example, when we apply<br>
a CVE patch to pseudo-native or rpm-native, or do some slight changes<br>
in their do_compile, "smart/opkg upgrade" will download/install *all*<br>
the packages since all of the packages' PR are bumped.<br>
<br>
Here are some rough suggestions to fix this problem, and please feel<br>
free to give your suggestions.<br>
1) Do not use do_package's task for bumping PR, the easiest way<br>
is simulate manually bump PR -- only bump PR when the recipe<br>
itself's checksum is changed.<br>
<br>
2) Add a new task for PRServer, redefine its task hash for bumping<br>
PR, for example, this task hash only considers RDEPENDS (no<br>
DEPENDS), and drop any native dependencies.<br>
<br>
I prefer the first way, and an alternative way maybe add a var so that<br>
the user can configure it:<br>
PR_CHECKSUM = "${BB_TASKHASH}" (current way)<br>
Or<br>
PR_CHECKSUM = "<recipe checksum>"<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Thanks<br>
<br>
Robert<br>
-- <br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org" target="_blank">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
</font></span></blockquote></div><br></div>