Skip to content

pub run should not build the current package if the command belongs to another package #1085

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 5, 2015 · 4 comments
Labels
closed-not-planned Closed as we don't intend to take action on the reported issue type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@DartBot
Copy link

DartBot commented Jun 5, 2015

<img src="https://avatars.githubusercontent.com/u/2049220?v=3" align="left" width="96" height="96"hspace="10"> Issue by sigmundch
Originally opened as dart-lang/sdk#20412


If you are in an application package, and invoke a command such as:

 pub run polymer:new_entry

pub will run barback and build all assets of the current package, but in reality it only needs to build the 'polymer' package in order to run that command. This results in a lot of overhead for large applications.

@DartBot
Copy link
Author

DartBot commented Jun 5, 2015

<img src="https://avatars.githubusercontent.com/u/405837?v=3" align="left" width="48" height="48"hspace="10"> Comment by zoechi


I tried if pub run polymer:new_element is already available and it took about 30 secs to print the message that new_element.dart wasn't found in polymer/bin even for consecutive calls. Is this related?

@DartBot
Copy link
Author

DartBot commented Jun 5, 2015

<img src="https://avatars.githubusercontent.com/u/2049220?v=3" align="left" width="48" height="48"hspace="10"> Comment by sigmundch


partially - the fact that it takes so long to give you an answer is likely related.

the fact that it's not found, might be something else. For that, could it be that something failed trying to install the latest version (0.12.1)?

pub-run tries to do a pub-get if the package installation doesn't seem up to date, but it doesn't communicate much of this information in the command line, so it could be taking a lot longer also trying to do package resolution if there was a failure in pub-get.

@DartBot
Copy link
Author

DartBot commented Jun 5, 2015

<img src="https://avatars.githubusercontent.com/u/405837?v=3" align="left" width="48" height="48"hspace="10"> Comment by zoechi


It works now (great btw!), but still takes 30 seconds.

@DartBot
Copy link
Author

DartBot commented Jun 5, 2015

<img src="https://avatars.githubusercontent.com/u/188?v=3" align="left" width="48" height="48"hspace="10"> Comment by nex3


This will be covered by issue #1087.


Added WontFix label.

@DartBot DartBot added type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) wontfix labels Jun 5, 2015
@DartBot DartBot closed this as completed Jun 5, 2015
@nex3 nex3 added closed-not-planned Closed as we don't intend to take action on the reported issue and removed wontfix labels Jun 5, 2015
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 type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Development

No branches or pull requests

2 participants