On 8/3/23 13:32, Ross Burton wrote:
> On 2 Aug 2023, at 22:35, Charlie Johnston via lists.openembedded.org 
> <[email protected]> wrote:
>> +++ b/meta/classes-recipe/packagefeed.bbclass
> 
> So this is a recipe-scope class which adds a task to generate a package feed 
> before do_build finishes.  I imagine the usecase would be that you add the 
> inherit to a packagegroup or image that defines the scope of the feed?

Currently the use case would be a new recipe defining the feed. That feed could 
simply contain a packagegroup, or multiple packages or packagegroups. I did 
consider leaving it up to the user to determine if the recipe were
also a packagegroup or image or similar but I currently have packagefeed 
inherit nopackages. I could be convinced to go back on that.

> Personally I’ve often doing `bitbake package-index` to use the local feed on 
> my target, but this class wouldn’t be useful because I’m not just building a 
> single image and if I want to use the feed it’s often because I want to add a 
> new package that wasn’t in the image before.   All I want is a way to ensure 
> that the deploy directory has an up to date feed in, am I right in thinking 
> this class doesn’t solve my usecase?
> 
> Cheers,
> Ross
I don't think the changes address your use case as-is. If you used a 
packagefeed recipe to build all your packages and used that packagefeed's 
directory as the local feed, it might work but you would have to add the 
missing package to the packagefeed recipe (or a packagegroup in that recipe).
I'm targeting the use cases where the feeds will be deployed publicly for use 
with images and (hopefully) for some future quality of life improvements to 
BUILD_IMAGES_FROM_FEEDS. I'm open to any ideas that might cover other uses. 

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

Reply via email to