Skip Menu |

This queue is for tickets about the File-Copy-Recursive CPAN distribution.

Report information
The Basics
Id: 68000
Status: rejected
Priority: 0/
Queue: File-Copy-Recursive
People
Owner: Nobody in particular
Requestors: SHAW [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: Wishlist
Broken in: 0.38
Fixed in: (no value)

History Show all quoted text
  Fri May 06 18:52:42 2011 SHAW [...] cpan.org - Ticket created
Subject: fmove() really copies the file, why not do a move()?
Hello, is there any reason why fmove() uses File::Copy::copy instead of File::Copy::move, which will fallback to copy() if necessary? [sshaw@localhost trunk]$ ls -i Y 129044042 Y [sshaw@localhost trunk]$ perl -MFile::Copy::Recursive=fmove -e'fmove shift, shift or die $!' Y Z [sshaw@localhost trunk]$ ls -i Z 129043037 Z Maybe it's to avoid the platform specific behavior of rename().. Nevertheless it would be nice if fmove() actually move()ed the file.
  Fri May 06 19:02:10 2011 dmuey [...] cpan.org - Correspondence added
On Fri May 06 18:52:42 2011, SHAW wrote: Show quoted text
> Hello, is there any reason why fmove() uses File::Copy::copy instead of > File::Copy::move, which will fallback to copy() if necessary? > > [sshaw@localhost trunk]$ ls -i Y > 129044042 Y > [sshaw@localhost trunk]$ perl -MFile::Copy::Recursive=fmove -e'fmove > shift, shift or die $!' Y Z > [sshaw@localhost trunk]$ ls -i Z > 129043037 Z > > > Maybe it's to avoid the platform specific behavior of rename().. > Nevertheless it would be nice if fmove() actually move()ed the file.
Yeah, currently it copies and if successful removes it. That was due to rename() sys dependent behaviors and some File::Copy problems that I believe have been addressed since. This will be addressed in the upcoming modernization.
  Fri May 06 19:02:10 2011 The RT System itself - Status changed from 'new' to 'open'
  Fri May 06 19:02:10 2011 dmuey [...] cpan.org - Status changed from 'open' to 'rejected'