Allow support for extensions in a subdirectory of the linked repo (to allow mono-repo setups)

[joseph-isaacs]

Hey,

We at vortex (https://github.com/spiraldb/vortex), are trying to add a vortex extension (duckdb/community-extensions#368) to this repo.

We want to keep this extension source in the main vortex repo, which it seems is not possible under the current setup. We want to place the extension in a subdirectory. Can we add a way to specify the subdirectory that the extension can be found at, maybe such as in description.yml add a path

repo:
  github: ...
  ref: 
  path: path/to/dir

What do you think or would you prefer another approach to achieve this?

[carlopi]

Hi @joseph-isaacs, I moved the issue here since it's more relevant.

I think proper path would be adding an optional input like relative_path or equivalent to https://github.com/duckdb/extension-ci-tools/blob/main/.github/workflows/_extension_distribution.yml, and when that is set move to the correct subfolder.

That would allow (once that is in) to then modify community_extensions's own CI to allow passing down this extra parameter here: https://github.com/duckdb/community-extensions/blob/main/.github/workflows/build.yml#L89.

Would that make sense to you?
If you want to contribute a PR, for the first or both steps, it would be amazing.

[joseph-isaacs]

Great, thanks Ill do this today

[joseph-isaacs]

The first part: #172

[joseph-isaacs]

And the community ext side duckdb/community-extensions#376