What initially attracted me to puppet wast that puppet described state and
not (in general) actions to achieve that state. Yet, I, too, was initially
confued that to manage symlinks I needed to manage "files" which had
something to "ensure" called "symlink". To make sure a directory is absent I
have to use this same "file" approach.
So, +1
Please, let us move to managing symlinks and recursive file copies, but do
look closely at splitting out directories and files as well.
~Charles~
On Mon, Mar 21, 2011 at 8:53 PM, Nigel Kersten <ni...@puppetlabs.com> 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, and
> even experienced users often don't know how combining symlinks/content
> management is going to work.
>
> How would people feel about at least splitting out these into their own
> types?
>
> * symlinks
> * recursive file copies
>
> The intersection of files and directories isn't that big a deal, but
> we could split out directories too if we wanted.
>
> Thoughts?
>
>
> --
> Nigel Kersten
> Product, Puppet Labs
> @nigelkersten
>
> --
> 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.
