Hello,
We are running perl, v5.6.1 built for
MSWin32-x86-multi-thread
Binary build 630 provided by ActiveState Tool Corp
It has a C:PerllibFileCopy.pm with the following
comment:
# Note that this module implements only *part* of the API
defined by
# the File/Copy.pm module of the File-Tools-2.0 package.
However, that
# package has not yet been updated to work with Perl 5.004,
and so it
# would be a Bad Thing for the CPAN module to grab it and
replace this
# module. Therefore, we set this module's version higher
than 2.0.
$VERSION = '2.03';
I just downloaded the File-Tools zip archive because there
has been an
interest
in the File::Recurse module it includes. File-Tools also
contains a
Copy.pm.
When I ran ppm install File-Tools.ppd, the modules were
installed in
C:PerlsitelibFileCopy.pm
C:PerlsitelibFileRecurse.pm
C:PerlsitelibFileTools.pm
I now have two modules with the same name and the lib
version is loaded
by default.
Would it be safe to delete the Copy.pm from the lib
directory? The
modules appear to
provide different functions for instance the lib version
exports the
following:
 EXPORT = qw(copy move);
EXPORT_OK = qw(cp mv);
the site/lib version exports only these and doesn't discuss
move, mv at
all:
EXPORT=qw(copy copydir);
EXPORT_OK=qw(copy copydir cp);
I know I could have the alter the INC order to
c:/perl/site/lib
C:/Perl/lib
C:/Perl/site/lib
but I'm concerned that this could potentially cause other
issues.
I am hoping that someone familiar with these modules
specifically,
or the best way to handle name conflicts in general, can
provide
insight into the preferred/safest approach?
Thanks in advance,
Paula
_______________________________________________
PPM mailing list
PPMlistserv.ActiveState.com
http://listserv.ActiveState.com/mailman/listinfo/ppm
|