For symlinks, that won't work unless the sourcedir is absolute, or calculated properly relative to the destdir. I don't see a disclaimer there for that, so I imagine people will be using it naively in a broken way.
For example, the following won't work:
$ mkdir src dst
$ touch src/foo
$ ln -s src/foo dst/bar
It doesn't work because the kernel will be trying to find dst/src/foo
when dst/bar is referenced. The symlink actually needs to be created
non-intuitively as:
$ ln -s ../src/foo dst/bar
Perhaps if your code computed the proper relative path from an
apparent relative path for symlinks, it'd be more useful.
| [reply] [d/l] [select] |
D'oh! That's what I get for not testing that bit... *sighs*
=cut
--Brent Dax
There is no sig.
| [reply] |
File::Spec's methods rel2abs() and abs2rel() are a convenient way to handle relative and absolute pathing. Also, why not use one of the Getopt::* modules instead of parsing the flags by hand? The performance might not be quite as good, but it does print a warning when someone types an unknown option.
«Rich36»
| [reply] |