Skip to content

Pub: installed name should be based on pubspec name, not URL #3494

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

Closed
DartBot opened this issue Jun 11, 2012 · 4 comments
Closed

Pub: installed name should be based on pubspec name, not URL #3494

DartBot opened this issue Jun 11, 2012 · 4 comments
Labels
closed-not-planned Closed as we don't intend to take action on the reported issue
Milestone

Comments

@DartBot
Copy link

DartBot commented Jun 11, 2012

This issue was originally filed by [email protected]


My pubspec looks like:

name: 'googlefoo-samples'
dependencies:
  googlefoo:
    git: https://code.google.com/p/google-foo-dart-client

The intent being to import as #import('package:googlefoo/...');
However this gets installed as packages/google-foo-dart-client, and can only be imported as 'package:google-foo-dart-client/...'.
Since the names are specified in the pubspec, is there any reason not to use them?

(I can't change the project name, it's a cross-language convention).

@kasperl
Copy link

kasperl commented Jun 11, 2012

Added Area-Pub, Triaged labels.

@munificent
Copy link
Member

Added this to the M1 milestone.

@nex3
Copy link
Member

nex3 commented Sep 5, 2012

Pub now requires the name in the pubspec to match the name extracted from the Git repo. Allowing the sort of renaming suggested in this issue would break transitive dependencies.


Added WontFix label.

@DartBot
Copy link
Author

DartBot commented Jun 5, 2015

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

@kevmoo kevmoo added closed-not-planned Closed as we don't intend to take action on the reported issue and removed resolution-wont_fix labels Mar 1, 2016
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-not-planned Closed as we don't intend to take action on the reported issue
Projects
None yet
Development

No branches or pull requests

5 participants