The pmtools POD commands will be the easiest to port to Perl6, but there's one obstacle – most pmtools POD commands require knowledge of Perl6's configuration, which we don't have yet in Pugs (no Config.pm). So I'm writing a tool in Perl6 (as I'm trying to eat our own dogfood) that will take the output of pugs -V and generate a Perl6 Config.pm from that output. (Yes, I know this should probably occur during the Pugs build process, but I don't have a huge amount of time for pmtools-perl6, so I'm chopping pmtools-perl6 into small, easy to program (for me) pieces.)
A minor problem is that my copy of Win32 pugs cannot find $EXECUTABLE_NAME when using it from -e. Pugs can use $EXECUTABLE_NAME OK from a Perl6 program – just not the -e command line. If anyone has an explanation as to why this must be so, please let me know.
hcchien writes: Taiwan will host the Open Source Developer's Conference on 7-8 April 2007. We are taking proposals for talks (in Chinese or English) until the end of January. More details will be available from the conference website when we have it ready. If you have any questions, please mail to email@example.com.
The latest version of Win32::API, marked v0.46, should now correctly install even from the CPAN shell. Finally!