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

[sigmundch]

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]

This comment was originally written 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?

[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]

This comment was originally written by @zoechi

---

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

[nex3]

This will be covered by issue #20482.

---

Added WontFix label.

[DartBot]

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