PR Service and eSDK
For some reason I thought if PR service was enabled, when the eSDK was generated it would export the pr service information and include it within the eSDK.
I'm not finding the file, or even code that does this. Am I having a fever dream, or is there code that should be doing this?
What I'm trying to build is an eSDK that the user can use devtool and construct a new version of a package, then they can deploy the new package within their package feed to update their targets. Without the PR service in the eSDK, there won't be any way to get a correct PR number.
--Mark
Quoted 10 lines · Mark Hatle
For some reason I thought if PR service was enabled, when the eSDK was generated it would export the pr service information and include it within the eSDK.
I'm not finding the file, or even code that does this. Am I having a fever dream, or is there code that should be doing this?
What I'm trying to build is an eSDK that the user can use devtool and construct a new version of a package, then they can deploy the new package within their package feed to update their targets. Without the PR service in the eSDK, there won't be any way to get a correct PR number.
I know we copy bb_unihashes.dat into the eSDK with code in populate_sdl_ext.bbclass for this reason for hashequiv.
We do have prserv export and import code but I'm not sure anyone has integrated it with eSDK, or if there is integration, I can't spot it atm. I wondered if it copied the prserv database from the build directory over to assist with this issue but again, I can't spot it.
Cheers,
Richard
Quoted 12 lines · Richard Purdie
Quoted 10 lines · Mark Hatle
For some reason I thought if PR service was enabled, when the eSDK was generated it would export the pr service information and include it within the eSDK.
I'm not finding the file, or even code that does this. Am I having a fever dream, or is there code that should be doing this?
What I'm trying to build is an eSDK that the user can use devtool and construct a new version of a package, then they can deploy the new package within their package feed to update their targets. Without the PR service in the eSDK, there won't be any way to get a correct PR number.
Quoted 7 lines
I know we copy bb_unihashes.dat into the eSDK with code in populate_sdl_ext.bbclass for this reason for hashequiv.
We do have prserv export and import code but I'm not sure anyone has integrated it with eSDK, or if there is integration, I can't spot it atm. I wondered if it copied the prserv database from the build directory over to assist with this issue but again, I can't spot it.
Ok, this confirms what I am seeing then. Maybe it was discussed and was never implemented. I'll look at where the unihashes.dat is copied over and look to do the export... and then import in the setup script.
--Mark
Quoted 8 lines
Cheers,
Richard