To be fair I'd argue for that unless there a switch/toggle provided by upstream we always install manpages unless they have dependencies.

In D51016#1164419, @diizzy wrote:

To be fair I'd argue for that unless there a switch/toggle provided by upstream we always install manpages unless they dependencies.

I see your point, but I would counter with:

• In the ports tree there is a split, I'd prefer to stay consistent and maybe in production deploy setups people even don't need manpages at all.
• Not everyone needs the docs, but wants manpages. Especially on servers I consider docs as useless. Best example: lang/rust.

I wonder to what degree @lev is still active because back then I took over all of this Subversion-related ports. Anyone else?

I'd value consistency over granuality that adds complexity but that's a personal opinion. If it works and Poudriere is happy I don't have any objections. Mentors?

In D51016#1166022, @diizzy wrote:

I'd value consistency over granuality that adds complexity but that's a personal opinion. If it works and Poudriere is happy I don't have any objections. Mentors?

Tried all combos before creating the review...

In D51016#1166054, @jrm wrote:

I also lean towards always installing man pages, unless there is some obscene dependency or an upstream toggle. I can also appreciate the value in providing the option.

There are cases where pandoc is required for manpages which requires ghc, etc. Quite some dependency tree. Best counterexample for docs is rust: 80% docs, 20% rust.

No maintainer response, can we use timeout here?