Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid

Re: copy, cp or syscopy of File::Copy?

by Anonymous Monk
on Feb 24, 2013 at 11:38 UTC ( #1020391=note: print w/replies, xml ) Need Help??

in reply to copy, cp or syscopy of File::Copy?

Makes no difference and "cp" isn't documented

I've never had a problem in over a decade, so I won't UTSL to try to decipher what rurban is talking about -- outburst without substance

Replies are listed 'Best First'.
Re^2: copy, cp or syscopy of File::Copy?
by rurban (Scribe) on Feb 25, 2013 at 23:20 UTC
    outburst without substance?
    if you have no idea what you are talking about, don't do it. if you never had a problem you are probably not deep enough into it, and you obviously never looked into the differences and accepted the wrong defaults.

    copy was the simple idea of perl IO copying, block per block, allowing handles, but it did not care about OS specific settings, like preserving permissions or ownership. This was a big issue over and over and p5p never cared. This was fixed finally a few releases ago (2.15 exactly), but there are still older perls around which use the old simple copy, loosing file attributes. The problem is mostly in os-compat Makefiles, which does use ExtUtils::Command cp for copying files, i.e. executables or shared libs, which loose there x bit after that treatment.

    syscopy uses the system provided syscopy and preserves attribs on most OS, and cp uses the cp(1) utility with filenames, if available.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1020391]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others browsing the Monastery: (4)
As of 2018-05-27 05:46 GMT
Find Nodes?
    Voting Booth?