On 26.04.2013 12:19, Jonathan Gazeley wrote:
I use puppet forge to install various modules on my puppetmaster. I'm
thinking about the build process if I build a new puppetmaster. Manually
reinstalling the modules is prone to error if I forget which modules I
used to have.
I looked at this module
On Wed, May 15, 2013 at 10:48 AM, Nikola Petrov wrote:
> I can second that. Not sure why puppetlabs decided to invent yet another
> package system with it's own problems and metadata definition and
> updates specifics
>
While I'm not disagreeing that this is a pain, I think part of the
difficult
I can second that. Not sure why puppetlabs decided to invent yet another
package system with it's own problems and metadata definition and
updates specifics
--
Nikola
On Fri, Apr 26, 2013 at 09:02:53AM -0400, Trevor Vaughan wrote:
> I usually package the modules that I want in the native package
On Fri, Apr 26, 2013 at 3:19 AM, Jonathan Gazeley <
jonathan.gaze...@bristol.ac.uk> wrote:
> How have other people handled this?
>
In addition to Puppet's built-in `puppet module` tool, there's a project
called librarian-puppet that lets you express your Forge modules in a
bundler like way. http:
I usually package the modules that I want in the native package manager of
the system.
Much easier to track and the 'package' statement works just fine.
Trevor
On Fri, Apr 26, 2013 at 6:19 AM, Jonathan Gazeley <
jonathan.gaze...@bristol.ac.uk> wrote:
> Hi people,
>
> I use puppet forge to ins
