pinning a crate in a remote monorepo (i.e., using --use=URL) does not setup GPR_PROJECT_PATH
I'm not sure if the existing behaviour is intended or not.
When pinning to a remote create in a monorepo, you can provide the URL and the crate name and Alire will add the dependency. However, when you examine the environment of the enclosing crate, the GPR_PROJECT_PATH is set to the root of the monorepo, not to the root of the crate within the monorepo. Consequently, the build will not find the dependency's project file.
For example, if this is the folder structure of the remote repo:
/monorepo/dependency/alire.toml
/monorepo/dependency/project.gpr
Then when you pin the dependency crate, the GPR_PROJECT_PATH is set to /monorepo, not /monorepo/dependency.
I can update the alire.toml environment to add the path, but I think it should probably be done automatically.
How does funding with Polar work?
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too