On Thu, 25 May 2023 at 23:54, Charlie Johnston <[email protected]> wrote:
> I can see a couple of potential options:
>
> 1. Come up with a way to ensure that the do_package_index task is only run 
> once per bitbake invocation after all other packaging tasks. As far as I can 
> tell, there's not a way to enforce this with my current design. It also 
> doesn't address the problem of packages already in the deploy directories.
> 2. Add more scaffolding to create a packagefeed class with potentially its 
> own deploy directory and which only includes index files for its 
> dependencies. That seems like a lot more effort than my change but might 
> address the concerns more completely.
> Any feedback or thoughts on those ideas?

You could try doing something like what buildhistory and similar
classes do, that is, hook into bb.event.BuildCompleted:
https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-metadata.html#events

Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#181763): 
https://lists.openembedded.org/g/openembedded-core/message/181763
Mute This Topic: https://lists.openembedded.org/mt/99118888/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to