-
Notifications
You must be signed in to change notification settings - Fork 229
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
Handle relative git-url-paths correctly when --directory #2919
Conversation
643d105
to
6f0b483
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you PTAL - especially the add-part?
@@ -90,9 +90,14 @@ class GlobalPackages { | |||
// dependencies. Their executables shouldn't be cached, and there should | |||
// be a mechanism for redoing dependency resolution if a path pubspec has | |||
// changed (see also issue 20499). | |||
PackageRef ref; | |||
try { | |||
ref = cache.git.source.parseRef(name, {'url': repo}, containingPath: '.'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Technically, we're going to write the pubspec.yaml
somewhere other than .
, so the containingPath
should be something like $PUB_CACHE/global_packages/<package>/
, shouldn't it?
I'm not sure it matters here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't write it to disk (yet), so it should not matter...
No description provided.