On Sep 12, 2009, at 23:02, Ivan Rambius Ivanov wrote:
Hm, I remember doing a macports installation on one machine and I did
not have this problem. On the current one, however, I used port
selfupdate. Do you think this may be the reason?
Only the MacPorts Installer package on the disk image do
out to be that $PREFIX/man, in my case /opt/local/man is not in
>> $MANPATH. I checked $HOME/.profile:
>>
>> #
>> # Your previous .profile (if any) is saved as .profile.mpsaved
>> # Setting the path for MacPorts.
>> export PATH=$HOME/bin:/opt/local/bin:/opt/l
On Sep 12, 2009, at 08:00, Ivan Rambius Ivanov wrote:
I am using MacPorts 1.8 and noticed that man(1) does not find the
manual pages for programs installed as mac ports. The reason turned
out to be that $PREFIX/man, in my case /opt/local/man is not in
$MANPATH. I checked $HOME/.profile
Hello,
I am using MacPorts 1.8 and noticed that man(1) does not find the
manual pages for programs installed as mac ports. The reason turned
out to be that $PREFIX/man, in my case /opt/local/man is not in
$MANPATH. I checked $HOME/.profile:
#
# Your previous .profile (if any) is saved as
On Aug 12, 2009, at 7:42 PM, Shawn Protsman wrote:
It didn't change the result. Apple's man page [for perl items] still
takes precedence. Any ideas? I wonder if this has anything to do
with the man#p dir that the macports perl man page is stored in?
"opt/local/share/man/man{1,3}p"
Yes, th
On Aug 12, 2009, at 10:14 AM, Shawn Protsman wrote:
The Apple installed manpages load before the macport manpages though
my path displays otherwise.
Example:
] echo $MANPATH
/opt/local/share/man:/usr/share/man:/usr/local/share/man:/usr/X11/share/man
] man perlcheat | grep 'perl v5.&
The Apple installed manpages load before the macport manpages though
my path displays otherwise.
Example:
] echo $MANPATH
/opt/local/share/man:/usr/share/man:/usr/local/share/man:/usr/X11/share/man
] man perlcheat | grep 'perl v5.'
perl v5.8.8
On 2008-10-28 19:42:48 -0500, Ryan Schmidt wrote:
> On Mac OS X 10.4 (and earlier), Apple provides no /private/etc/man.conf.
>
> On Mac OS X 10.5 (and later?), Apple does provide /private/etc/man.conf
> and it does set MANPATH. It's not really MacPorts' place to modify
>
On Oct 28, 2008, at 02:28, Erwan David wrote:
Okay, so now I'm thoroughly confused. OS X (10.5.5) reported
nothing when
I did an 'echo $MANPATH' and wouldn't show me a man page for
'port'. So, I
added 'export MANPATH=/opt/local/share/man:$MANPATH'
>
> Okay, so now I'm thoroughly confused. OS X (10.5.5) reported nothing when
> I did an 'echo $MANPATH' and wouldn't show me a man page for 'port'. So, I
> added 'export MANPATH=/opt/local/share/man:$MANPATH' to my .profile and
> now
On Oct 27, 2008, at 23:57, Shawn Protsman wrote:
On Oct 27, 2008, at 6:27 PM, Vincent Lefevre wrote:
On 2008-10-27 20:01:48 -0500, Ryan Schmidt wrote:
Apple sets the MANPATH to "/usr/share/man:/usr/local/share/man:/usr/
X11/man" on Leopard for you. So at least Apple doesn&
On Oct 27, 2008, at 6:27 PM, Vincent Lefevre wrote:
On 2008-10-27 20:01:48 -0500, Ryan Schmidt wrote:
Apple sets the MANPATH to "/usr/share/man:/usr/local/share/man:/usr/
X11/man" on Leopard for you. So at least Apple doesn't think it
should
end with a colon.
Apple of
On 2008-10-27 20:01:48 -0500, Ryan Schmidt wrote:
> Apple sets the MANPATH to "/usr/share/man:/usr/local/share/man:/usr/
> X11/man" on Leopard for you. So at least Apple doesn't think it should
> end with a colon.
Apple often does things wrong. Try (while having
On Oct 27, 2008, at 19:26, Vincent Lefevre wrote:
On 2008-10-27 16:43:58 -0500, Ryan Schmidt wrote:
On Tiger and earlier, MANPATH is empty by default and so having /opt/
local/bin in PATH is sufficient. However on Leopard and I assume
later,
MANPATH is non-empty by default so you need to
On 2008-10-27 16:43:58 -0500, Ryan Schmidt wrote:
> On Tiger and earlier, MANPATH is empty by default and so having /opt/
> local/bin in PATH is sufficient. However on Leopard and I assume later,
> MANPATH is non-empty by default so you need to add /opt/local/share/man
> to MANPA
ports'?
Or add to .profile:
export MANPATH=/opt/local/share/man:$MANPATH
The latter. Using paths.d would append the MANPATH at the end, but
usually you want to add new items in front of the system provided
ones.
Normally you don't even need to do anything. Having /opt/loc
On Mon, Oct 27, 2008 at 08:57:42AM -0700, Shawn Protsman said:
> On Oct 27, 2008, at 7:22 AM, Robert Goldman wrote:
>
>> Isn't the right thing to edit /etc/man.conf so that the path -> man
>> translation works, and then make sure that your MANPATH environment
>>
On Oct 27, 2008, at 7:22 AM, Robert Goldman wrote:
Isn't the right thing to edit /etc/man.conf so that the path -> man
translation works, and then make sure that your MANPATH environment
variable is *not* set?
I think Shawn's problem was (at least possibly) not having /opt
ent
Isn't the right thing to edit /etc/man.conf so that the path -> man
translation works, and then make sure that your MANPATH environment
variable is *not* set?
I think Shawn's problem was (at least possibly) not having /opt entries
in /etc/man.conf.
BTW, for people like me who r
ports'?
Or add to .profile:
export MANPATH=/opt/local/share/man:$MANPATH
The latter. Using paths.d would append the MANPATH at the end, but
usually you want to add new items in front of the system provided
ones.
Normally you don't even need to do anything. Having /opt/loc
;?
> >
> > Or add to .profile:
> >
> > export MANPATH=/opt/local/share/man:$MANPATH
>
> The latter. Using paths.d would append the MANPATH at the end, but
> usually you want to add new items in front of the system provided ones.
Normally you don't ev
Rainer Müller wrote:
Shawn Protsman wrote:
To my surprise I got no entry found when I did a 'man port'. What is
the recommended method to add port manpages to the path?
Create a '/etc/paths.d/macports'?
Or add to .profile:
export MANPATH=/opt/local/share/man:$MANPATH
Shawn Protsman wrote:
> To my surprise I got no entry found when I did a 'man port'. What is
> the recommended method to add port manpages to the path?
>
> Create a '/etc/paths.d/macports'?
>
> Or add to .profile:
>
> export MANPATH=/opt/local/s
To my surprise I got no entry found when I did a 'man port'. What is
the recommended method to add port manpages to the path?
Create a '/etc/paths.d/macports'?
Or add to .profile:
export MANPATH=/opt/local/share/man:$MANPATH
__
I ended up adding /opt/local/man to MANPATH and "man port" works.
There was also an existing symbolic link from /opt/local/man to
/opt/local/share/man
as someone else mentioned.
_
Boo! Scare away worms, viruses and so
25 matches
Mail list logo
