svn commit: r367002 - head/devel/cmake

[John Marino]

On 9/2/2014 17:42, Adam Weinberger wrote:
> On 2 Sep, 2014, at 11:40, John Marino <freebsd.contact at marino.st>
>>>> I understand that installing man pages is mandatory, that it
>>>> should not be OPTION controlled.  A lot of ports use sphinx so
>>>> I don't know what the big deal about sphinx in particular is,
>>>> but lets say it's something else far worse.   man pages could
>>>> be pregenerated and installed from $FILEDIR right?  So there
>>>> are alternatives, but unless I'm wrong about the policy using
>>>> OPTIONS is not one of them (but I'm wrong a lot, so let's see
>>>> what the answer is).
>>> 
>>> How do you mean mandatory?
>>> 
>>> OPTIONS_DEFINE+=	MANPAGES OPTIONS_DEFAULT+=	MANPAGES 
>>> MANPAGES_CONFIGURE_ON=	--sphinx-man
>>> 
>> 
>> By mandatory, I mean that a port that does that is violating
>> policy. Documentation is optional (DOCS) but manpages are not.
>> That's what I've understood.  I've see ports that tried the above
>> and I've removed code of that equivalent.
>> 
>> John
> 
> If it’s on by default I don’t see the problem. Who are we to decide
> that nobody should ever be allowed to build a port without manpages?
> 

If it's the policy, it's the policy.

However, I sorta kinda think a <bsd.port.mk> option to not package man
pages for all ports may be coming for embedded usage.  That won't solve
this dependency that you are trying to fix, but it will solve the "i
don't need manpages for any port" issue.

Sphinx is not like tex though.  It's really not a big deal practically
speaking.

John