(1) That seems useful (eg. install plugin_foo and plugin_foo_test in one command). Maybe, by default, omitting the `--name` parameter could install all plugins found in the specified repo/hash.
(2) I think there's theoretical value in this, but cloning is somewhat cheap so it's probably not worth the effort, especially with (1) implemented (as you said). On Fri, Mar 22, 2013 at 3:20 PM, Michal Mocny <[email protected]> wrote: > Huge +1. > > Questions: > 1. Could we allow installing multiple plugins/subdirectories from within > the same repo in one step. Support wildcards? (i.e. cordova plugin add > --repo=....git --version=hash --name="*") > 2. Should we cache git repos so we dont need clone over and over for each > plugin and app. I think this isn't necessary if you just allow (1) and/or > make it easy to --link to local folders by default (then you cache > manually). > > > On Fri, Mar 22, 2013 at 2:28 PM, Braden Shepherdson <[email protected] > >wrote: > > > This has all of my +1s. Especially if our testing story is a dependent > > plugin, this is way more convenient than two repos. > > > > Braden > > > > > > On Fri, Mar 22, 2013 at 2:19 PM, Brian LeRoux <[email protected]> wrote: > > > > > I'm into it. > > > > > > On Fri, Mar 22, 2013 at 11:11 AM, Max Woghiren <[email protected]> > > wrote: > > > > The main technical ask here is the ability to specify a plugin as { > git > > > > repo, commit hash, subdirectory } instead of just { git repo, commit > > > hash }. > > > > > > > > On Fri, Mar 22, 2013 at 2:05 PM, Brian LeRoux <[email protected]> wrote: > > > > > > > >> Would have the benefit of enabling a plugin, and plugin-test > existence > > > >> in a single repo. Consolidates a lot of tooling. Lets discuss more > > > >> herein > > > >> > > > > > >
