perl-docs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stas Bekman <>
Subject Re: [PATCH] DocSet on Win32
Date Wed, 03 Apr 2002 12:26:20 GMT
Per Einar Ellefsen wrote:
> At 09:23 03.04.2002, Stas Bekman wrote:
>> Per Einar Ellefsen wrote:
>>  > - 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.
> Yes, I was thinking about that. I'll package it up. Any idea on how to 
> get a CPAN ID quickly?

I don't think it takes long, just follow the steps in the PAUSE CPAN doc

Also check that somebody hasn't already implemented this.

Me thinking that this may belong to the core functionality so you may 
want to run this through p5p as well.

>>  > - 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.
> URI might be useful if someone thinks my idea of adding Apache module 
> documentation might be useful :) We could then fecth pod sources 
> remotely from.... (fill the blank, I'm not so sure)

True, we may do this in the future. Need to have a reliable source 
though. For now I've added a link to

>>  > 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?
> Well, the scripts from the DocSet distribution, html2ps and 
> docset_build, get installed correctly into the Perl binary dir when make 
> install is run.
> However, no makefile is run when extracting the site repository from 
> CVS, so we can't automate it. I think the best thing to do would be to 
> simply add a line to the Readme:
> To be able to run bin/build and bin/docset_build under Win32, you'll 
> have to go through the following steps (being placed in the modperl-docs 
> base directory):
>  cd bin
>  pl2bat build
>  pl2bat docset_build
> Now, being placed in your base directory, you can execute "bin\build" 
> with any normal options. Make sure to redo the above steps if build or 
> docset_build are changed in CVS.

or we can add a Makefile.PL to do the work for the users. The question 
is where make install should install things.

For now I think an INSTALL doc will do, later if we use Makefile.PL for 
other things we may integrate this too.

After all bin/build is already a convenience script

> (is makeindex used? If so you need to add makeindex each time).

yes, it's used to create an index for the search.

>>  > 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)
> No, the Perl Package Manager shouldn't be involved here. This is during 
> the PDF generation.
> I'll try to look up where the error is coming from, but the problem is 
> that the build takes an aweful lot of time, and has a tendency of 
> crashing my computer if I don't follow slosely on what it's doing.

there are two stages in creating a pdf. html => ps => pdf. Which stage 
does it fail at?

You don't have to rebuild the whole thing just to test something.
Simly adjust the timestamp of the file and then rebuild without -f. I 
always something like this:

% touch src/download/binaries.pod && bin/build

or if I want the pdf, I add the -f flag

Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker     mod_perl Guide --->

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message