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

Jump to bottom

If a git path in a pubspec is relative interpret it relative to the pubspec #8570

Closed
munificent opened this issue Feb 16, 2013 · 7 comments
Closed

If a git path in a pubspec is relative interpret it relative to the pubspec #8570

munificent opened this issue Feb 16, 2013 · 7 comments
Assignees
@munificent
Labels
type-enhancement A request for a change that isn't a bug

Comments

@munificent
Copy link
Member

You can use a file path as a git dependency. When you do, it's interpreted as relative to the package directory of the root package. It should be resolve as relative to the pubspec that contains the dependency (like relative path deps are).
@munificent
Copy link
Member Author

Added Community-StarterBug label.

@kasperl
Copy link

kasperl commented Jul 10, 2014

Removed this from the Later milestone.
Added Oldschool-Milestone-Later label.

@kasperl
Copy link

kasperl commented Aug 4, 2014

Removed Oldschool-Milestone-Later label.

@DartBot
Copy link

DartBot commented Aug 27, 2014

This comment was originally written by @kaendfinger

Shouldn't this have a PatchesWelcome label?

@munificent
Copy link
Member Author

Patches are welcome on every bug! :)

I think the "PatchesWelcome" usually means "we don't intend to put time into this ourselves, but will take a contribution from someone else for it", but I'm not positive since I haven't used that tag.

@munificent
Copy link
Member Author

Patches are welcome on every bug! :)

Well, let me qualify that by saying contributions are welcome on every bug, but we do like to know a bit about what the contributor has in mind before seeing an actual patch. We don't always do a great job of writing down the full context behind some bug, so there may be some tribal knowledge to impart before a contributor gets coding.

@munificent munificent self-assigned this Aug 27, 2014
@DartBot DartBot mentioned this issue Jun 5, 2015
Closed
@DartBot
Copy link

DartBot commented Jun 5, 2015

This issue has been moved to dart-lang/pub#449.

@DartBot DartBot closed this as completed Jun 5, 2015
@kevmoo kevmoo added type-enhancement A request for a change that isn't a bug and removed triaged labels Mar 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@munificent munificent

Labels
type-enhancement A request for a change that isn't a bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kevmoo @munificent @kasperl @DartBot