From: "Mark Hatle" <mark.hatle@kernel.crashing.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] PR Service and eSDK
Date: Tue, 23 Mar 2021 17:47:15 -0500 [thread overview]
Message-ID: <a98e3c52-54f2-e131-1c53-f688ec2589ed@kernel.crashing.org> (raw)
In-Reply-To: <48a1fdaf1535daf49500ed7ae3551bc7099e4940.camel@linuxfoundation.org>
On 3/23/21 5:45 PM, Richard Purdie wrote:
> On Tue, 2021-03-23 at 17:34 -0500, Mark Hatle wrote:
>> 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.
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
> Cheers,
>
> Richard
>
>
>
>
>
prev parent reply other threads:[~2021-03-23 22:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 22:34 PR Service and eSDK Mark Hatle
2021-03-23 22:45 ` [OE-core] " Richard Purdie
2021-03-23 22:47 ` Mark Hatle [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a98e3c52-54f2-e131-1c53-f688ec2589ed@kernel.crashing.org \
--to=mark.hatle@kernel.crashing.org \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.