HP3000-L Archives

February 2002, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Mark Bixby <[log in to unmask]>
Reply To:
Mark Bixby <[log in to unmask]>
Date:
Mon, 11 Feb 2002 16:51:39 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (38 lines)
Donna Garverick wrote:
 > Mark Bixby wrote:
 >
 >
 >> Donna Garverick wrote:
 >>
 >>> how do i get the perl man pages to work?  got'em of course....but....
 >>>      -
 >>>
 >> export MANPATH=/PERL/PUB/man:$MANPATH
 >>
 >
 > ok...i can do that.  (do i want the perl man pages at the front of my
 > manpath?)

It's up to you.  I don't think the Perl man pages are likely to clash with any
of the MPE FOS man pages, so front vs. back doesn't matter.

 > i can even set up a local .profile file to automatically update my man
 > path.  but is that the 'normal' way of handling such a thing?  with man
 > pages for different applications being installed wherever....i can see
 > this turning into a messy maintenance problem.               - d

Updating MANPATH is the 'normal' way, either in the .profile of individual
users, or for everybody in /etc/profile.local.

You only have to do this once though after the installation or update of an
application.  And for my modern ports, and I think almost everything of mine
follows my current standardized layout, you only need to change MANPATH on the
first installation to refer to /ACCOUNT/CURRENT/man and that will still work
after subsequent updates.
--
[log in to unmask]
Remainder of .sig suppressed to conserve expensive California electrons...

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2