On Oct 25, 2005, at 3:35 PM, Joshua Hoblitt wrote:
On Tue, Oct 25, 2005 at 06:31:43AM +0200, Fran?ois PERRAD wrote:
The subroutine check_progs defined in lib/Parrot/Configure/Step.pm
is not
portable (doesn't work on MSWin32).
On MSWin32, the real filename of a program is prog.exe, prog.com,
prog.bat
or prog.cmd , so if -x 'prog' is not enough.
Sorry about that. Did the old probe mechanism work on win32?
I suggest the use of the module File::Which (see the attached patch).
But I don't know if everybody is agree to depend of this module.
File::Which is a rather small amount of code in a single file so
I'd be
inclined to include it in the Parrot tree rather then reinventing the
wheel. I've always been puzzled as to why there isn't a core perl5
module with this functionality.
What do others think about this proposal?
-J
I think that module is small enough and useful enough for the build
process to include in parrot if we need to (and copying it in is
better than rewriting it from scratch), but...
I think this would be a good time (esp. after discussion on IRC) to
introduce the possibility of creating a CPAN bundle that is required
for parrot development. This would give us an external dependancy
(con), but it would allow us to remove all the bundled CPAN modules
that we currently have (good), and allow us to easily add or subtract
the required modules as necessary.
We could have a config check early on that checks for the presence of
the required bundled modules and bails, with instructions on how to
grab the Bundle from CPAN and install it. We can tie the required
bundle version to svn revision (or release version, or both) of parrot.
