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

[email protected] (Peter Prymmer) Sat, 1 Dec 2001 13:14:13 +0000 (GMT)
Newsgroups perl.macperl.porters
Message-ID <[email protected]>
On Fri, 30 Nov 2001, Scott R. Godin wrote:

> Unix does this when you install a module - updates a file called
> "perllocal.pod" to list what modules were recently installed/updated
> locally.
>
> the output it contains looks somewhat like this:
>
>        Tue Apr 24 12:44:41 2001: Module the Class::Multimethods
>        manpage
>
>        o   installed into:
>            /home1/users/sgodin/perl/lib/perl5/site_perl
>
>        o   LINKTYPE: dynamic
>
>        o   VERSION: 1.70
>
>        o   EXE_FILES:

Thanks for the illustration.

> And no, Peter, I don't *think* it does, but I'd have to do a lotta
> poking around -- I haven't noticed this anywhere so I'm pretty sure it
> does not. Chris?

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.   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?  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.
Also: would any harm come from running "BuildHelpIndex" for each module
that is installed?  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.

Peter Prymmmer