-
Notifications
You must be signed in to change notification settings - Fork 230
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
Self-references in generated .packages files point to the pubcache. #1294
Comments
Thanks @nex3 ! |
w00t. Thank you! On Thu, Jul 9, 2015 at 12:48 PM, Seth Ladd notifications@github.com wrote:
Phil Quitslund |
I'm not sure this is fixed. Running
|
Oh wait... @nex3 : maybe we just need to update the |
Running pub from the repo seems to do the right thing.
So I think updating |
Whoops. Looks like I failed to re(sync) before I built. I just confirmed that |
This will help avoid issues like #1294 in the future. R=rnystrom@google.com, rnystrom@gmail.com Review URL: https://codereview.chromium.org//1227913009 .
Self-references are not properly encoded. They point to the pubcache rather than the local source.
For example, given a package
foo
, the.packages
reference will look something like this:whereas it should look more like:
(Note that pub symlinks do this special-casing. Which is to say we just need to get the
.packages
file URIs to agree with pub's symlink prior art.)In the current state URI resolution for self-references in
analyzer
all fail.The text was updated successfully, but these errors were encountered: