Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Taruntej Kanakamalla <tarun@centricular.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
	sebastian@centricular.com, nirbheek@centricular.com
Subject: Re: [OE-core] [PATCH v3] gstreamer1.0-plugins-rs: add new package
Date: Fri, 29 May 2026 19:27:45 +0530	[thread overview]
Message-ID: <4d3fe3f57026a8b8bb407bc9bca85c7c2dbf1dde.camel@centricular.com> (raw)
In-Reply-To: <CANNYZj-yJ_CMvCq6bXu8RHiDDCNUbQcOTrJANZoKfZ5SMhoNkA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1944 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 2119 bytes --]

  parent reply	other threads:[~2026-05-29 14:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 13:34 [PATCH] gstreamer1.0-plugins-rs: add new package Taruntej Kanakamalla
2026-05-12 10:30 ` [OE-core] " Mathieu Dubois-Briand
2026-05-13  7:14   ` Taruntej Kanakamalla
2026-05-12 19:28 ` Peter Kjellerstedt
2026-05-13  7:25   ` Taruntej Kanakamalla
2026-05-13  7:56     ` Peter Kjellerstedt
2026-05-24  2:02       ` Taruntej Kanakamalla
2026-05-13  7:11 ` [PATCH v2] " Taruntej Kanakamalla
2026-05-13 10:19   ` [OE-core] " Alexander Kanavin
2026-05-13 11:23     ` Nirbheek Chauhan
2026-05-13 11:45       ` Alexander Kanavin
2026-05-13 12:02         ` Nirbheek Chauhan
2026-05-13 12:15           ` Alexander Kanavin
2026-05-13 13:10             ` Nirbheek Chauhan
2026-05-24  1:51         ` Taruntej Kanakamalla
2026-05-24  1:23   ` [PATCH v3] " Taruntej Kanakamalla
2026-05-24 10:12     ` [OE-core] " Alexander Kanavin
2026-05-25 17:06       ` Peter Kjellerstedt
2026-07-07  8:21         ` Taruntej Kanakamalla
2026-05-29 13:57       ` Taruntej Kanakamalla [this message]
2026-07-07  8:17     ` [PATCH v4] " Taruntej Kanakamalla
2026-07-08  6:20       ` [OE-core] " Richard Purdie
     [not found]       ` <18C03C30DCBC1651.550146@lists.openembedded.org>
2026-07-08  6:24         ` Richard Purdie
2026-07-14 10:55       ` [PATCH v5 1/2] cargo_c.bbclass: pass --libdir to cargo cinstall Taruntej Kanakamalla
2026-07-14 10:55         ` [PATCH v5 2/2] gstreamer1.0-plugins-rs: add new package Taruntej Kanakamalla
2026-07-15 11:37           ` [OE-core] " Mathieu Dubois-Briand
2026-07-15 13:50             ` Mathieu Dubois-Briand

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=4d3fe3f57026a8b8bb407bc9bca85c7c2dbf1dde.camel@centricular.com \
    --to=tarun@centricular.com \
    --cc=alex.kanavin@gmail.com \
    --cc=nirbheek@centricular.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sebastian@centricular.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox