A request to segregate man pages for shell built-ins

Matthew Seaman matthew at FreeBSD.org
Wed Oct 25 09:08:46 UTC 2017

On 25/10/2017 09:56, Sijmen J. Mulder wrote:
> Whilst I do appreciate builtin(1)'s comprehensiveness I too find it hard
> to nagivate.
> Op 25-10-2017 om 10:10 schreef Matthew Seaman:
>> In the case of eg. echo(1), I'd be happy to see the existing page for
>> the stand-alone echo refactored to cover all of the different flavours
>> of echo -- the behaviour is much the same in most use cases -- plus some
>> discussion on how the variants differ.
> This seems like a good solution. But, how would shells in ports deal
> with this? A builtin(1)-like foosh(1), or foosh_echo(1), foosh_case(1),
> etc?

Outside projects will do their own thing.  We can (as the FreeBSD
project) provide our own man pages for a FreeBSD port where we think
that what upstream provides is deficient, and we can submit those pages
upstream as good citizens are supposed to, but again, this relies
entirely on someone volunteering to step up and do the work.  However,
it's unlikely that we'd want to try and integrate or combine man pages
from external projects with base system manpages in any significant way.
 That's far too complex and fragile to be worth the effort.
/usr/share/man and /usr/local/man are different worlds.



More information about the freebsd-questions mailing list