Puppet users - Aug 2012 - issues with puppetdoc and missing symlink

I have a module with its files/ directory symlinked to a SVN checkout 
outside of the module path (specifically, to /shared_svn). (explanation 
below) in a few places within that directory structure, there are some 
dead symlinks. When I run puppetdoc on my modules and manifests, it dies 
with "Could not generate documentation: No such file or directory" 
because the file it''s looking for is a symlink to a non-existent file.

I know that the actual error is being generated in rdoc itself, 
specifically an Errno::ENOENT (no such file or directory) in rdoc.rb 
(for 1.8.7-p299, on line 177).

Is there any way to get puppetdoc to ignore a specified path, or paths?

Aside from patching puppetdoc itself, can anyone think of a way to work 
around this? Anything better than doing a second checkout of my configs 
without the offending SVN directory and running puppetdoc against that?

Thanks,
Jason

PS - The reason for this is a bit of a pain, but it''s a set of 
configuration files which are managed by puppet on new machines, and 
managed via a cron''ed svn update on older machines. The symlinks are
for
the older machines, and refer to local paths on them...

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.