Per Einar Ellefsen wrote:
 >
 > Hello everyone,
 >
 > Well, I got DocSet ported to Win32. It wasn't such a big task
 > afterwards.

:)

What was changed:
 > - replaced call to `which` with a portable which function in
 > DocSet::Util (taken from Apache::Build in modperl-2.0 and made to use
 > the PATHEXT env variable on WinNT: I can re-submit this one into the
 > modperl-2.0 tree if you think that'll be useful, it finds the specified
 > file terminated by .exe, .bat, etc..

Better yet release it on CPAN. I'm sure other people will find this very
useful.

 > - use perl %ENV instead of `env` to set PERL5LIB whenh calling
docset_build

cool!

 > - had to replace all regexes that used a directory/file path, and use
 > quotemeta() there, because the backslahes created illegal escape
sequences.

simply adding \Q to the beginning of a regex is just fine, unless it has to be run in the big loop, where doing quotemeta once is faster.

 > - changed some things before calling URI in DocSet::Doc; it not, the
 > directory name would be considered part of the host name and thus not
 > tried to be opened. So I replaced \ with /, as that'll open the file
 > correctly.

Well, I may scratch the use of URI altogether. I've simply planned to be
able to handle any URI as a source, but currently only file paths are
used. For now your patch is fine.

 > I think that's it.
 > For bin/build to work correctly, there must also be .bat versions of
 > build and docset_build. I'm not sure about how to handle this in a
 > general way, maybe the bat files should be integrated into CVS or
 > something? I need some tips on that.

How other cross-platform packages that install binaries handle this?

 > Furthermore, there was a problem with html2ps: it begins with a line
saying
 > : # Use Perl
 > When converting it to .bat (as it is when it's installed into perl/bin),
 > that colon is a problem. It should be removed.

is this ok?

#!perl
eval 'exec perl -S $0 "$@"'
  if $running_under_some_shell;

 > For the PDF version, it all seems to have been build correctly, but
 > after a loong wait (it takes a long time, even on a pretty decent
 > computer here, but I guess that's normal),  I get the following errors:
 > Invalid Parameter - \svs..ppm
 > Output file write error --- out of disk space?
 > Invalid Parameter - \sds..ppm
 > Output file write error --- out of disk space?
 > Invalid Parameter - \sr0..ppm
 > Invalid Parameter - \sr0..ppm
 > Invalid Parameter - \sr0..ppm
 > Invalid Parameter - \sr0..ppm
 > Invalid Parameter - \su0..ppm
 > Invalid Parameter - \su0..ppm
 > Invalid Parameter - \su0..ppm
 > Invalid Parameter - \su0..ppm
 >
 > Does anyone know where this is coming from? I don't have the guts to try
 > and debug it now. Please tell me if you know where it's coming from
 > (DocSet or Ghostscript?)

what's ppm? is it the perl package manager?

what operations do you get these errors from? you should see it by building in the verbose more (-v)

__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to