Sub components in managed lib cause errors (PACMAN-1066)

[malachib]

The Component Manager version

2.1.1

ESP-IDF Version

v5.3.2

python Version

3.11.2

Operating System

Debian x64

Browser (for https://components.espressif.com Issues)

Chrome

Description

I have a use case, say 3 libraries:

• shared
• lib1
• lib2

lib1 and lib2 both consume shared (as if shared were an sdk)
I would like to consume all 3 of these under the banner of one managed component.

A crude comparison would be the usage of esp_lcd component as contained in esp-idf repository.

If done locally via a path specified in idf_component.yml, I am able to do so
If done remotely (as we typically do with esp components) via git: I get this error:

ERROR: The "path" field in the manifest file
"/tmp/tmp8jpiou7b/src/PGESP-74/managed/components/lib1/idf_component.yml"
  does not point to a directory.  You can safely remove this field from the
  manifest if this project is an example copied from a component repository.

To Reproduce

Issue is reproducible and observable in my proof of concept area here:

PGESP-74

In particular, app_remote exhibits the issue while app_local does not.

If more exposition is required, please let me know.

Expected behaviour

I expect to consume a managed component and gain access to contained components also present in its repository.

Additional info

I am experimenting with the notion of a "meta" component which grabs everything. I am not married to that approach, it just felt the most viable.

The broader context for this is a graphics library with a core and then support drivers. I want to pull in the core and also the (optional) support drivers in one fell swoop using esp component manager.

I have checked existing issues and online Documentation

• I confirm I have checked existing issues and online Documentation.

[kumekay]

Hello @malachib I was able to reproduce your issue, however, the git dependency with local dependencies is the case we didn't cover well through the initial design. We will discuss possible solutions and I'll update this issue.

[malachib]

Yes please share your thinking, and great work on the component system in general by the way!

[malachib]

Hi, it's been a while. This continues to be something that is of interest. Any progress on your side?

[XDanielPaul]

Hi @malachib!

I am sorry for taking too long on our part. I will be taking over this issue.

We've recently fixed a similar issue, related to resolving override_path in git dependencies, so I suggest using it over path as a temporary workaround.

The way to support path is feasible, so we will try to support it as well in a near future. I'll keep you updated!

[XDanielPaul]

Hi @malachib, we've released a new IDF Component Manager version, which should fix your error

ERROR: The "path" field in the manifest file
"/tmp/tmp8jpiou7b/src/PGESP-74/managed/components/lib1/idf_component.yml"
  does not point to a directory.  You can safely remove this field from the
  manifest if this project is an example copied from a component repository.

Could you please verify?