On Fri, Jul 30, 2010 at 8:13 AM, Curtis Jewell p...@csjewell.fastmail.uswrote:
So the build process can't symlink without checking for support for it
first. (Catalyst DOES run on Win32, after all, as well as the Unixen.)
Of course.
Here's an svn export of an app:
$ find . | wc -l
35677
$
Oh, that patch will break when used on an existing tree, so don't use. And
I'm not clear how distclean will work with the symlinks.
So, if destination is already a symlink is there anything to do? Assume
it's already linked.
And if it's a regular dir then do the rcopy?
I'm using this just to
When I run Makefile.PL the Module::Install::Catalyst step can take a number
of minutes -- it just took five minutes on one machine just now. I assume
that's because of the recursive copy.
Does the build process require actual copies or could symlinks be used to
speed up this process?
--
Bill
On those machines which allow symlinks, unfortunately...
So the build process can't symlink without checking for support for it
first. (Catalyst DOES run on Win32, after all, as well as the Unixen.)
--Curtis
On Fri, 30 Jul 2010 07:46 -0700, Bill Moseley mose...@hank.org
wrote:
When I run
