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

> In README_DEVELOPER.md:
>
> >
> > -For example, Puppet checked out into `/workspace/src/puppet` using `git
> > -checkout https://github.com/puppetlabs/puppet` <https://github.com/puppetlabs/puppet> in `/workspace/src` can be used
> > -with the following actions.  The trick is to symlink `gems` to `src`.
> > +This last line extracts the gem specification from the gem and places it locally in the file 'puppet.gemspec'.
> > +
> > +Next, prepare the workspace to be picked up in the current user's gems list.
> > +The trick is to symlink `gems` to `src` and ensure that puppet is found in the GEM_PATH.
>
> Well, as near as I can tell, the point of this section would be to have a
> checked out dev instance which you can call with a simple
>
> $ puppet
>
> instead of a
>
> $ bundler exec puppet
>
> Either because you don't like typing that, or you have other reasons for
> not involving bundler.
>
> I don't think this should be the default setup process, but it seems like
> something one might want to do, and this at least records the steps needed
> to accomplish it.
>
> We could more prominently mark the section as "minor voodoo you probably
> don't need unless you know you need it"
>
Ah, in this scenario we should probably just mention installing
rubygems-bundler will avoid the need to wrap everything in bundle exec,
provided the bin stubs are in the PATH.


-- 
*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%!*