Installing a ConfigFile kills symlinks

[naapuri]

I had a ConfigFile? statement for /foo/bar/baz.conf. On the client, /foo was a symlink to /real-foo, and there the bar/ subdir didn't exist.

When installing baz.conf, the bcfg2 client killed the /foo -> /real-foo symlink and created directories /foo/ and /foo/bar/.

I expected the client not to mind that /foo/ is a symlink.

[desai]

I can't replicate this problem in my test environment, but this patch both cleans up the code and adds more logging to indicate why it is (re)creating paths.

[desai]

Since this isn't reproducable with the new code, I am closing this ticket for now.