Hi Alex,

On Sun, 2026-05-24 at 12:12 +0200, Alexander Kanavin wrote:

> Sorry, no. Carrying and maintaining this gigantic Cargo.lock in  
> oe-core isn't right. You need to place and maintain it upstream.

Understood. I wanted to ship the lock file along with the recipe only for the 
purpose of `update_recipes:append` task, in which it was updating a few 
dependencies that use git as source to rather use their crates.io versions in 
the lock file so that those get appended to the SRC_URI in the -crates.inc file.

But going forward we are going to have this directly in the release to avoid 
editing the manifest or lock files locally in the recipe. I will submit a new 
patch moving back to using the upstream once we have the next gst-plugins-rs 
release in the coming days.

> Or, perhaps a better approach is to maintain individual recipes for  
> each of the plugins, and fetch them using crate://crates.io/...
> 
> I think they're all available there?  
> [https://crates.io/search?q=gst-plugin](https://crates.io/search?q=gst-plugin)
> 
> The recipes themselves will likely be very short, and share most of  
> the metadata through a common .inc file.

I have explored the per plugin recipe approach and probably the recipes look 
cleaner with this approach, but I am not much in favour of this because:

1. We could generate as many recipes as the plugins using a script, but this 
process of managing multiple recipe files could get tedious as the number of 
plugins grow.
2. There are multiple plugins which have common dependencies and with per 
plugin recipe approach, these plugins would have duplicate copies of those 
common dependencies in their respective CARGO_VENDORING_DIRECTORY. So, that 
will result in increased disk usage for the build directory. On contrary the 
single workspace recipe (as in this V3 patch) will download only one copy per 
dependency, all of them will be in single location.

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

  • Re: [OE-core] [PATCH v3] g... Peter Kjellerstedt via lists.openembedded.org
    • Re: [OE-core] [PATCH ... Taruntej Kanakamalla via lists.openembedded.org

Reply via email to