Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 Jul 2006 22:06:36 +0400
From:      Sergey Matveychuk <sem@FreeBSD.org>
To:        "[LoN]Kamikaze" <LoN_Kamikaze@gmx.de>
Cc:        Brooks Davis <brooks@one-eyed-alien.net>, freebsd-ports@freebsd.org
Subject:   Re: makewhatis from ports
Message-ID:  <44BE74AC.1080501@FreeBSD.org>
In-Reply-To: <44BE64E2.1050905@gmx.de>
References:  <44BCF5F0.7090809@gmx.de> <44BDD5AB.3060801@FreeBSD.org>	<44BE00DA.4030901@gmx.de> <20060719151014.GB32499@lor.one-eyed-alien.net> <44BE64E2.1050905@gmx.de>

next in thread | previous in thread | raw e-mail | index | archive | help
[LoN]Kamikaze wrote:
> Brooks Davis wrote:
>> On Wed, Jul 19, 2006 at 11:52:26AM +0200, [LoN]Kamikaze wrote:
>>> Sergey Matveychuk wrote:
>>>> [LoN]Kamikaze wrote:
>>>>> I've got a Makefile where I install man pages int PREFIX/man/man1 and the ports system nicely compresses them, but it does not make them available for whatis. Should I run makewhatis PREFIX/man manually or is there a way this is supposed to be done? The Porter's Handbook chapter 5.9 does not mention whatis.
>>>> It will be done with weekly script 320.whatis.
>>>> I think we have no practice to do it when a port is installed.
>>>>
>>> Thanks for the reply.
>>>
>>> That means I don't have to take care of it, still it would make more
>>> sense to let the ports take care of it.
>> If we're going to do it, setting MAN variables should cause it to happen
>> in bsd.port.mk rather than having it done adhoc.
>>
>> -- Brooks
> 
> That's what I was expecting in the first place. And it should be trivial to accomplish for someone who has the privileges to work on the Ports system.

Everyone have privileges to work on the Ports system. :)

-- 
Dixi.
Sem.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44BE74AC.1080501>