Nigel Kersten wrote:
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.
A tentative -1 from me. I haven't had
Am 22.03.2011 23:52, schrieb Nigel Kersten:
> If you're enabling recursive copies for Directories, then you're also
> supporting the 'source' property, and you're also supporting the
> "links => {follow, manage, ignore}" parameter and recurse and
> recurselimit
I see your point.
As an alterna
On Tue, Mar 22, 2011 at 3:06 PM, Christian Kauhaus wrote:
> Am 22.03.2011 02:53, schrieb Nigel Kersten:
>>
>> The intersection of files and directories isn't that big a deal, but
>> we could split out directories too if we wanted.
>
> From the user's perspective, it's more like the other way round
Am 22.03.2011 02:53, schrieb Nigel Kersten:
The intersection of files and directories isn't that big a deal, but
we could split out directories too if we wanted.
From the user's perspective, it's more like the other way round. We should
not let implementation issues guide the design of the man
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
hav
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
