Re: [Puppet Users] ANNOUNCE: Puppet Module Tool version 0.3.4

2011-08-10 Thread Scott Smith
I don't see any statement claiming that it'll automagically get put into the
right place.

On Tue, Aug 9, 2011 at 6:35 PM, John Warburton jwarbur...@gmail.com wrote:


 On 10 August 2011 11:24, Scott Smith sc...@ohlol.net wrote:

 How will it know which directory in your modulepath to install it?

 That's the point. You need to explicitly cd to the correct modulepath
 directory first. Per my example at the bottom


 $ cd /path/to/forge/modules
 $ puppet-module install puppetlabs-lvm

 John

 --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To post to this group, send email to puppet-users@googlegroups.com.
 To unsubscribe from this group, send email to
 puppet-users+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/puppet-users?hl=en.


-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.



Re: [Puppet Users] ANNOUNCE: Puppet Module Tool version 0.3.4

2011-08-10 Thread Ken Barber
Hi Scott,

I think its fair enough thing to expect it to do something like this ...

Incidentally, there is already a feature request for this:

http://projects.puppetlabs.com/issues/3789

Do you want to watch/vote for it ...? Or you can always provide a
patch ... we won't complain :-).

ken.

On Wed, Aug 10, 2011 at 8:13 PM, Scott Smith sc...@ohlol.net wrote:
 I don't see any statement claiming that it'll automagically get put into the
 right place.

 On Tue, Aug 9, 2011 at 6:35 PM, John Warburton jwarbur...@gmail.com wrote:

 On 10 August 2011 11:24, Scott Smith sc...@ohlol.net wrote:

 How will it know which directory in your modulepath to install it?

 That's the point. You need to explicitly cd to the correct modulepath
 directory first. Per my example at the bottom

 $ cd /path/to/forge/modules
 $ puppet-module install puppetlabs-lvm

 John

 --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To post to this group, send email to puppet-users@googlegroups.com.
 To unsubscribe from this group, send email to
 puppet-users+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/puppet-users?hl=en.

 --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To post to this group, send email to puppet-users@googlegroups.com.
 To unsubscribe from this group, send email to
 puppet-users+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/puppet-users?hl=en.




-- 
Join us for PuppetConf, September 22nd and 23rd in Portland, OR:
http://bit.ly/puppetconfsig;

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.



[Puppet Users] ANNOUNCE: Puppet Module Tool version 0.3.4

2011-08-09 Thread James Turnbull
Hi all

We've just released version 0.3.4 of the puppet-module tool used to
create and retrieve modules from the Puppet Labs Forge
(http://forge.puppetlabs.com).

You can update using Ruby gems:

$ gem install puppet-module

There are several important changes in this release:

* Add ability to install modules with hyphens
* Add check for symlink when installing
* Install modules to their name not full name
* Add semantic version support

The major functional difference is in how modules are installed, for
example a module named:

jamtur01-apache

Will now be installed into your module path as:

apache

You can find the code and full commit logs at:

https://github.com/puppetlabs/puppet-module-tool

Regards

James Turnbull

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.



Re: [Puppet Users] ANNOUNCE: Puppet Module Tool version 0.3.4

2011-08-09 Thread John Warburton
On 10 August 2011 08:47, James Turnbull ja...@puppetlabs.com wrote:

 We've just released version 0.3.4 of the puppet-module tool used to
 create and retrieve modules from the Puppet Labs Forge
 (http://forge.puppetlabs.com).

 excellent


 Will now be installed into your module path as:

 apache


No, actually it won't install into your module path: This archive is then
automatically unpacked into a new directory under your current directory --
unless you are in your module path

So reading the section Install a module release it says You can then add
this *module directory* to your Puppet configuration files to use it. My
mind went huh? Seems like I'm not the only one (
http://groups.google.com/group/puppet-users/browse_thread/thread/6ae174f50e5f7364
)

After 20 minutes of googling and Mr Google telling me there was a section on
the forge in Chapter 8 of Pro Puppet, I read the examples and worked out
that I need to install into modulepath as set in my puppetmaster config file

modulepath seems to be the key text missing in the instructions  examples.
It may be obvious for people who have been doing this, but first timers, its
not quite there.

So, if I was doing this, I'd have something like:

[environment]
modulepath = /path/to/environment/modules:/path/to/forge/modules

$ cd /path/to/forge/modules
$ puppet-module install puppetlabs-lvm

[BTW this doesn't sit too well with me - seems to manual. I may end up
creating an RPM/pkg for each module to install...]

Hope this helps someone out there

John

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.



Re: [Puppet Users] ANNOUNCE: Puppet Module Tool version 0.3.4

2011-08-09 Thread Scott Smith
How will it know which directory in your modulepath to install it?
On Aug 9, 2011 6:02 PM, John Warburton jwarbur...@gmail.com wrote:
 On 10 August 2011 08:47, James Turnbull ja...@puppetlabs.com wrote:

 We've just released version 0.3.4 of the puppet-module tool used to
 create and retrieve modules from the Puppet Labs Forge
 (http://forge.puppetlabs.com).

 excellent


 Will now be installed into your module path as:

 apache


 No, actually it won't install into your module path: This archive is then
 automatically unpacked into a new directory under your current directory
--
 unless you are in your module path

 So reading the section Install a module release it says You can then
add
 this *module directory* to your Puppet configuration files to use it. My
 mind went huh? Seems like I'm not the only one (

http://groups.google.com/group/puppet-users/browse_thread/thread/6ae174f50e5f7364
 )

 After 20 minutes of googling and Mr Google telling me there was a section
on
 the forge in Chapter 8 of Pro Puppet, I read the examples and worked out
 that I need to install into modulepath as set in my puppetmaster config
file

 modulepath seems to be the key text missing in the instructions 
examples.
 It may be obvious for people who have been doing this, but first timers,
its
 not quite there.

 So, if I was doing this, I'd have something like:

 [environment]
 modulepath = /path/to/environment/modules:/path/to/forge/modules

 $ cd /path/to/forge/modules
 $ puppet-module install puppetlabs-lvm

 [BTW this doesn't sit too well with me - seems to manual. I may end up
 creating an RPM/pkg for each module to install...]

 Hope this helps someone out there

 John

 --
 You received this message because you are subscribed to the Google Groups
Puppet Users group.
 To post to this group, send email to puppet-users@googlegroups.com.
 To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
 For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.


-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.



Re: [Puppet Users] ANNOUNCE: Puppet Module Tool version 0.3.4

2011-08-09 Thread John Warburton
On 10 August 2011 11:24, Scott Smith sc...@ohlol.net wrote:

 How will it know which directory in your modulepath to install it?

That's the point. You need to explicitly cd to the correct modulepath
directory first. Per my example at the bottom

$ cd /path/to/forge/modules
$ puppet-module install puppetlabs-lvm

John

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.