Jan you are absolutely correct about not deleting the html folder.

In my response I was describing my attempts and their results.
As a safety measure I renamed the html folder so I could easily recover.

When I made those attempts, my intent was to determine the path of least resistance
to accomplish the update of those html files that could not be displayed.

As a results of these attempts I can summarize my findings as follows:

UpdateHTML creates html files only if they do not currently exist...existing html files are not overwritten. It essentially creates html files destined for the bin, lib, and site folders in the html folder. The ActivePerl installation can populate some htmls in these folders that UpdateHTML would not generate.

If you installed a module using CPAN , you can use UpdateHTML to generate the html files without prep work.

If you installed a module using ppm then the only truly safe way is to locate and delete the html files installed by ppm for that module and then run UpdateHtlm. The bin, lib, and site folders may contain html files that were populated by
the ActivePerl installation so they probably should  not be deleted.

You MUST NOT delete the html folder or empty it.

my final 2 cents





----- Original Message ----- From: "Jan Dubois" <[EMAIL PROTECTED]> To: "'renard'" <[EMAIL PROTECTED]>; "'Active Perl Lister'" <activeperl@listserv.ActiveState.com>
Sent: Monday, August 29, 2005 6:18 PM
Subject: RE: ActivePerl Documentation in 5.8.7


On Sun, 28 Aug 2005, renard wrote:
It took me 4 attempts to successfully update the html files

Attempt 1: Ran UpdateHTML(1), it took several minutes and exited
without any error message. Tests revealed that the html files would
still not be displayed.

Attempt 2 Renamed the html folder, effectively
deleting it. Ran UpdateHTML(1), it exited immediately without any
error message. No html folder had been created.

You should not delete the complete html folder.  Just remove the
html\site directory (and maybe html\bin and html\lib), but leave
everything else as is.  If you run UpdateHTML() now it should just
regenerate the missing subdirectories.

The DocTools packages uses the existence of various files in the
html directory as flags to determine which kind of TOC to generate
etc.

Also, not all files in that tree are generated from POD, so by
removing the complete tree you also loose many of the non module-
specific help pages.

Cheers,
-Jan



_______________________________________________
ActivePerl mailing list
ActivePerl@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs

Reply via email to