Re: [MacPerl-Porters] [ macperl-Bugs-486790 ] Shuck file problems

At 13:14 +0000 2001.12.01, Peter Prymmer wrote:
>Apparently, as Thomas has pointed out, the "MacPerl.podhelp" index file
>would need to be updated then the "BuildHelpIndex" script would need to be
>run.

Not really.  The MacPerl Help file is a DB file; you can manipulate it
directly with DB_File (which is what I've done in the past).  Something
like:

	$dbm{'My::Module'} = 'pod:site_perl/My/Module.pm';

I might have the syntax off by a bit.


>The appending of the information to perllocal.pod typically
>gets done my your make utility as part of the `make install` build target,
>hence the appendage to perllocal.pod should apparently be added to
>ExtUtils::MM_MacOS.pm.  I wonder: would it hurt the index to have
>"MacPerl.podhelp" updated to "add" perllocal.pod each time a module has
>`BuildProgram install` run?

Probably adding to perllocal.pod and adding to MacPerl Help would be in
order.  Patches welcome, of course.  :-)  The problem is that the "make
install" process is kinda weird.  It can work, though.  See
Mac::BuildTools::make_install().  I am not sure offhand where and how it
happens on Unix.


>One would need to ensure that one entry only
>is made for perllocal.pod but that could be arranged with a hash of
>"MacPerl.podhelp" pod document names for keeping track of the uniq ones.

I didn't think it bothered to check for unique entries in perllocal.pod on
Unix.

>Also: would any harm come from running "BuildHelpIndex" for each module
>that is installed?

It's unnecessary.  Also, it might produce unpredictable results, since I am
not sure if it is designed to be re-run.  As noted, I don't think it's
necessary, though.

>If there is harm then perhaps a stub for an empty
>perllocal.pod could be left in place as part of the installation of Perl.

I think both adding perllocal.pod as a stub, and adding to it on install,
and adding entries with DB_File on install to MacPerl Help, are all in
order.

-- 
Chris Nandor                      [email protected]    http://pudge.net/
Open Source Development Network    [email protected]     http://osdn.com/