Would updating Puppetfile upstream with latest versions of every
module make sense to everyone?
As discussed here just because its added here doesn't mean it needs to
be installed.
Benefit would be saving people from checking tags of all modules to
confirm latest.
Process would be someone creates a new module or update of
puppet-mymodule and sends PR for Puppetfile to be updated with this
latest tag? You could always keep local copy on merge.

Other option which I think would be even better is if option similar
to "puppet module update modulename" would work for boxen? Boxen
module list, boxen module update modulename.


On 10/22/13, Will Farrington <notifications@github.com> wrote:
>>  github "dnsmasq",    "1.0.0"
>> +github "foreman",    "1.0.0"
>
> @ericanderson That's easily dealt with. We just use PATH for everything, so
> you can in your shell config put the path to your custom install of foreman
> in front of PATH.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/boxen/our-boxen/pull/426/files#r7147050

-- 
Sent from my mobile device