Re: [Puppet-dev] RFC: Splitting up the file{} type functionality.

2011-03-22 Thread Nigel Kersten
On Tue, Mar 22, 2011 at 4:13 AM, David Schmitt wrote: > On 22.03.2011 02:53, Nigel Kersten wrote: >> >> The file{} type can do all of the following: >> >> * manage single files >> * manage directories >> * manage symlinks >> * manage recursive file copies >> >> The intersection of all these bits o

Re: [Puppet-dev] RFC: Splitting up the file{} type functionality.

2011-03-22 Thread Nick Moffitt
Nigel Kersten: > The file{} type can do all of the following: > > * manage single files > * manage directories > * manage symlinks > * manage recursive file copies I tend to use different defaults for the different types, so I would love to be able to do: File { mode => 0444 } Di

Re: [Puppet-dev] RFC: Splitting up the file{} type functionality.

2011-03-22 Thread David Schmitt
On 22.03.2011 02:53, Nigel Kersten wrote: The file{} type can do all of the following: * manage single files * manage directories * manage symlinks * manage recursive file copies The intersection of all these bits of functionality makes it difficult to understand exactly what is going on when y

Re: [Puppet-dev] RFC: Splitting up the file{} type functionality.

2011-03-21 Thread James Turnbull
Nigel Kersten wrote: The file{} type can do all of the following: * manage single files * manage directories * manage symlinks * manage recursive file copies The intersection of all these bits of functionality makes it difficult to understand exactly what is going on when you're new to Puppet,

Re: [Puppet-dev] RFC: Splitting up the file{} type functionality.

2011-03-21 Thread Markus Roberts
> I thing that recursive copies are the type that fits worst into the current > code; I suggest we move that out and then wait and see if symlinks should > follow or not. > The match with symlinks qua symlinks is pretty hideous as well. It just looks a little less lumpy because it's been hammered

Re: [Puppet-dev] RFC: Splitting up the file{} type functionality.

2011-03-21 Thread Daniel Pittman
I thing that recursive copies are the type that fits worst into the current code; I suggest we move that out and then wait and see if symlinks should follow or not. Regards, Daniel -- Puppet Labs Developer –http://puppetlabs.com Daniel Pittman Contact me via gtalk, email, or phone: +1 (877)

[Puppet-dev] RFC: Splitting up the file{} type functionality.

2011-03-21 Thread Nigel Kersten
The file{} type can do all of the following: * manage single files * manage directories * manage symlinks * manage recursive file copies The intersection of all these bits of functionality makes it difficult to understand exactly what is going on when you're new to Puppet, and even experienced us