-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Vendored dependencies are saved with a full file path specific to the machine #83
Comments
Could you give me an example
|
We have packages stored in the
|
Oh wow, just realizing how late my reply is here. Sorry about that 😅 Is the issue here the header of the lock file, or the lock file itself having these absolute instead of relative paths? |
No worries.
My
|
The first part commented out is the |
When you have a dependency configured like
"name @ {root:uri}/vendor/name.1.zip"
the requirements.txt file will have the full path likefile:///home/user/code/project/vendor/name.1.zip
. Everything works when another person runs it on another machine, but the requirements file will have been updated to have the path on their machine, which causes git churn.Can the requirements.txt file store the entry with a relative path or keeping the
{root:uri}
present?The text was updated successfully, but these errors were encountered: