You are not logged in.

#1 2008-06-12 00:27:18

freakcode
Member
From: São Paulo - Brazil
Registered: 2007-11-03
Posts: 410
Website

Documentation matters? [ SOLVED ]

I'm wondering what's the rationale behind striping man pages from packages. Recently I enjoyed how great is FreeBSD documentation, both online documentation (FreeBSD handbook) and offline documentation with great covering of man pages.

While here, the package doesn't include a man page that is VITAL for something like Awesome, and the associated 'awesomerc'. Looking online is not an alternative, because the site doesn't contain direct access for the same content that is on the man pages. I'm using the Awesome case, but that happens with other packages.

Does documentation matter less for Arch? If so, why?

Last edited by freakcode (2008-06-12 01:00:20)

Offline

#2 2008-06-12 00:32:43

Allan
Developer
From: Brisbane, AU
Registered: 2007-06-09
Posts: 9,939
Website

Re: Documentation matters? [ SOLVED ]

The package should include man pages as it is generally Arch policy that man pages are enough...  So I would file a bug report for the package without them.  First do a "pacman -Ql <package>" to make sure man pages are not there but being missed somehow.

Offline

#3 2008-06-12 00:43:36

freakcode
Member
From: São Paulo - Brazil
Registered: 2007-11-03
Posts: 410
Website

Re: Documentation matters? [ SOLVED ]

The man page exists (/usr/share/man/man5), but I can't access. In fact, I can't access *various* man pages, beside the fact the files exists.

Any idea? Do I need to generate a catalog or something to 'man' start locating the files? From my past experience with Linux I guessed man was something that 'just works'.

Offline

#4 2008-06-12 00:45:01

Allan
Developer
From: Brisbane, AU
Registered: 2007-06-09
Posts: 9,939
Website

Re: Documentation matters? [ SOLVED ]

Check that you have merged /etc/profile.pacnew with /etc/profile and MANPATH is unset

Offline

#5 2008-06-12 01:00:05

freakcode
Member
From: São Paulo - Brazil
Registered: 2007-11-03
Posts: 410
Website

Re: Documentation matters? [ SOLVED ]

Right on the point. Now I can access most man pages I need.

Offline

#6 2008-06-12 06:51:38

Barrucadu
Member
From: Hull, England
Registered: 2008-03-30
Posts: 1,157
Website

Re: Documentation matters? [ SOLVED ]

I am having a similar problem, but that didn't fix it. I can only access manpages by running "sudo man", even when operating as root!

Offline

#7 2008-06-12 07:05:01

Allan
Developer
From: Brisbane, AU
Registered: 2007-06-09
Posts: 9,939
Website

Re: Documentation matters? [ SOLVED ]

Run "echo $MANPATH" and if it prints anything, find where it is set and nuke it.

Offline

#8 2008-06-12 23:32:16

MoonSwan
Member
From: Great White North
Registered: 2008-01-23
Posts: 815

Re: Documentation matters? [ SOLVED ]

There are online man pages too if you ever have need to use them due to space constraints or some other reason(s).


I'm torn apart between worlds. Basically, using vim in a highly visual environment with a lot of mouse features feels like soldering a lose wire to a motherboard with a Zippo and a needle, while working with ANY TEXT AT ALL with a "modern GUI" text editor feels like joining the London Philharmonic Orchestra with a Fisher-Price Laugh and Learn Magical Musical Mirror.  --Awebb

Offline

Board footer

Powered by FluxBB