Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug in relative paths in [sources] #3842

Open
KristofferC opened this issue Mar 13, 2024 · 0 comments
Open

Bug in relative paths in [sources] #3842

KristofferC opened this issue Mar 13, 2024 · 0 comments

Comments

@KristofferC
Copy link
Member

KristofferC commented Mar 13, 2024

IIUC, currently, all relative paths for packages (pkg.path) are considered relative to the manifest file. But in cases they are provided by a [sources] entry they should in fact be treated relative to the project file. This only matters if the project and manifest file are in different directories. That situation can occur when using the manifest = entry in the project file or when using the subproject functionality in #3841.

This is a bit annoying because I think it means we need to remember from where the path entry was retrieved.

@KristofferC KristofferC changed the title Probable bug in relative paths in [sources] Bug in relative paths in [sources] Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant