Re: Re: Config managers

[sutch]

in reply to Re: Config managers
in thread Config managers

This is a good last resort.

I've found that PPM is superior for Windows installations since it automatically adds a module's HTML documentation to ActivePerl's set of documentation (HTML files). I'm sure that this can be done manually, but I haven't spent the time to figure it out.

Are there instructions available for creating HTML pages from a module's POD and then linking it into ActivePerl's documentation?

Also, what other things does PPM handle that is specific for ActivePerl? I've noticed something about PPM3 registering installed modules with ActiveState.

[PodMaster]

Are there instructions available for creating HTML pages from a module's POD and then linking it into ActivePerl's documentation?

At first I used to use ActivePerl::DocTools. Soon after I wrote ActivePerl::DocTools::TOC::HTML::Podmaster. Around that time ActiveState started removing the pod from all the ActivePerl::* modules. I didn't like that very much, so I wrote Pod::Master. I now use Pod::Master exclusively.

Also, what other things does PPM handle that is specific for ActivePerl? I've noticed something about PPM3 registering installed modules with ActiveState.

I haven't seen anything about that, but then I don't have an ActiveState account, or buy any of ActiveStates producs (I get the free stuff). What you're describing are ActiveState Developer profiles (or something like that). I don't use that feature (apparently if you use ActiveState flavored TCL, Python ... you can also use PPM to manage those, but I don't use TCL, and I don't use ActiveState flavored Python).

update: if you don't bother to look at ActivePerl::DocTools::TOC::HTML::Podmaster, or look inside ActivePerl::DocTools, how you (or PPM for that matter) update the html is

perl -MActivePerl::DocTools -e UpdateHTML()

That's basically what PPM does after you use it to install a module.

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"

I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).

** The third rule of perl club is a statement of fact: pod is sexy.

[sutch]

Thanks for the information, and for Pod::Master.

After looking over the ActivePerl::DocTools::TOC source, I now see why I was oblivious to it: this module specifically excludes all ActivePerl:: modules from the table of contents (TOC).

Any chance of some future version of Pod::Master overriding the _BuildHashes method to allow for better user control of what does and doesn't go into the TOC?