in reply to Recursive File Copy question

On windows, I'd use xcopy /exclude:fileOfThingsToExclude src dst.

Eg. put \tmp\ & .svn\ on separate lines in fileOfThingsToExclude and tmp dirs off the root of any drive, and .svn\ dirs anywhere in a directory tree will be skipped.

Mostly because it will copy acls (or not as you need), and a bunch of other useful options. But also, because it's faster than pretty much anything else.


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

Replies are listed 'Best First'.
Re^2: Recursive File Copy question
by rovf (Priest) on Jul 22, 2008 at 08:34 UTC
    On windows, I'd use xcopy /exclude:fileOfThingsToExclude src dst

    Yes, but when I do this from perl, my program would not be portable to other platforms anymore.

    -- 
    Ronald Fischer <ynnor@mm.st>

      There are usually so many special cases to be dealt with when dealing with filesystems, that it doesn't make sense to try and use the same code on Win32 and *nix-like systems. So don't try:

      if( $^O eq 'mswin32' ) { ## use xcopy } elsif( $^O =~ m[(linux|unix|whatever)] ) { ## use something else } else { ## use another something else ## or throw up your hands in disgust. }

      What do I mean by special cases?

      1. *nix filesystems have:
        • a unified filespace;
        • soft & hard links;
        • chmod, chown, chgrp;
        • case-sensitivity;
        • Unicode filenames?;
        • other;
      2. Win32 filesystems have:
        • drives;
        • UNCs;
        • shares;
        • substs;
        • junctions;
        • streams;
        • attributes;
        • ACLs;
        • case-transparency;
        • long & short filenames;
        • Wide-character filenames;
        • other;
      3. Other non-disish/non-*nixish filesystems?

        ...

      Mixing all the special cases together and trying to deal with them in-line, is an exercise in frustration & complexity and is doomed to years of bugs and failures.

      Make a high-level, up-front decision as to which system you are on and then load a different module or use a different subroutine and keep the logic simple(r).


      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.