comment on

Definitely File::Find will be a good friend to make here. The &wanted sub can deal with collisions on the fly. The following is untested.

use warnings;
use strict;
use File::Find;
use File::Spec::Functions;
use Time::HiRes;
use File::Copy;

my $root = "/path/to/root"
find(\&wanted, $root);
sub wanted {
  if (File::Find::dir eq $root) {
    print "$_ is already in the root folder $root\n";
  } else {
    my $target = catfile($root, $_);
    if (-f $target) {
       my $microtime = join '.', Time::HiRes::gettimeofday();
       print "Filename collision, appending $microtime to $_ before mo
+ving\n";
       move($File::Find::name, $target . $microtime);
    } else {
      print "Moving " . $File::Find::name . " to $target\n";
      move($File::Find::name, $target)
    }
  }
}
[download]

There are probably saner ways to deal with collisions; Being able to know where it came from might be very nice.

In reply to Re: Flattening a directory tree in a filesystem by jellisii2
in thread Flattening a directory tree in a filesystem by steve

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


"be consistent"
	PerlMonks