H4 has asked for the wisdom of the Perl Monks concerning the following question:

I'm note sure whether this question should be posted here, but I'll just go ahead. Please redirect me if it shouldn't.

I am working with Active Perl 5.8.8 (build 819) under Win32. I want to install modules to a user-defined area. I followed the instructions on the ppm manpage, and it seems to work. The HTML docs are generated from the pod source, and the documentation table of contents perltoc.html is opened for write access (an error occurs if writing access is denied), but the TOC isn't changed, and the new manpages aren't linked into the TOC.

I am very sure that file and directory issues are not the reason. This is because, using (restrictive) default permissions, error messages are displayed. I even tried to install the module under Administrator account, with the same effect. Any ideas?

Replies are listed 'Best First'.
Re: Installing a module to a user area
by Anonymous Monk on Sep 15, 2008 at 12:45 UTC
    I followed the instructions on the ppm manpage, and it seems to work.
    Which instructions exactly?

    The HTML docs are generated from the pod source, and the documentation table of contents perltoc.html is opened for write access (an error occurs if writing access is denied), but the TOC isn't changed, and the new manpages aren't linked into the TOC.
    I don't think they were supposed do and as far as I know, only privlib, sitelib, and scriptdir are covered.

      Which instructions exactly? --> on the ppm manpage, under the 'ppm area init area' heading. I ran 'ppm area init area' afterwards. In the ppm GUI, I can see the new install area. I can even use the ppm GUI to install a CPAN package to the new area - only the docs aren't made available.

      I don't think they were supposed do --> that would be a pity. Sure it's not just something I'm doing wrong?

        I don't think so. If you grep ...lib/ActivePerl/DocTools for INC/@INC/PERL5LIB/PERLLIB/PPM, you won't find anything to indicate the toc would be updated

        Maybe there is a toc built in the new area? Either way, I'd contact activestate, they might fix it :)