On Wednesday, June 12, 2013, Josh Partlow wrote:

> In README_DEVELOPER.md:
>
> >
> > -To install the dependencies run: `bundle install` to install the dependencies.
> > +    $ bundle install
>
> Installing to a separate --path is generally my preferred method, but it's
> not a requirement for just getting the project set up. I'm thinking of just
> the minimal setup steps required to be able to run tests and work.
> Isolating the gems into a separate path is more for the benefit of not
> interfering with other projects which might not be using bundler.
>

Adding --path is the same number of setup steps, is our preferred method,
and will avoid problems down the road so lets go with adding --path.

> We could provide the minimal steps, and then note the --path variant and
> what it's benefit is?
>
We could, but it's the same number of steps either way and we can avoid the
note altogether. If we want to make a note then lets mention --path can be
omitted to install the dependencies into GEM_HOME, but I don't think a note
is necessary.

> One other question though --path .bundle/gems installs into bundler's own
> .bundle directory; is that going to collide with other bundler activities,
> like installing from git repositories?
>
It doesn't collide and it makes it easier to clean up; simply nuke the
.bundle directory.

-Jeff


-- 
*Jeff McCune <http://jeffmccune.com/>*
Join us at PuppetConf 2013 <http://bit.ly/pupconf13>, August 22-23 in San
Francisco*
**Register now and take advantage of the Early Bird discount - save 25%!*