Re: RFC: MacPorts policy should be that docs should not be built or installed by default

2019-09-20 Thread Ryan Schmidt
On Sep 19, 2019, at 23:40, Ken Cunningham wrote: > the documentation that comes along with many ports often seems like a heavy > and arguably needless burden: > I vote we expect ports to not include anything but a few man pages. > Everything else should be either left out, or an optional

Re: RFC: MacPorts policy should be that docs should not be built or installed by default

2019-09-20 Thread Blair Zajac
> On Sep 20, 2019, at 8:04 AM, m...@macports.org wrote: > > Hi Ken, > > > Thank you for bringing this up. We also need to discuss, as a group, how to > label documentation variants and sub-ports. Currently there is quite a > diversity. > > See https://trac.macports.org/ticket/58338. >

Re: RFC: MacPorts policy should be that docs should not be built or installed by default

2019-09-20 Thread Ralph Seichter
* Ken Cunningham: > I bet almost nobody ever looks at them, much less uses them. Well, I certainly do. On any UNIX-like system I expect at least man- pages for every installed command line utilty, configuration file, etc. Having locally installed docs is a requirement for working offline. I

Re: RFC: MacPorts policy should be that docs should not be built or installed by default

2019-09-20 Thread mf2k
Hi Ken, Thank you for bringing this up. We also need to discuss, as a group, how to label documentation variants and sub-ports. Currently there is quite a diversity. See https://trac.macports.org/ticket/58338 . I propose “docs” for a variant name

Re: RFC: MacPorts policy should be that docs should not be built or installed by default

2019-09-20 Thread Joshua Root
On 2019-9-20 14:40 , Ken Cunningham wrote: > the documentation that comes along with many ports often seems like a heavy > and arguably needless burden: > > - huge bloat > - lots of often onerous, massive, fussy build deps > - often takes as much time to sort out doc building as building the

RFC: MacPorts policy should be that docs should not be built or installed by default

2019-09-19 Thread Ken Cunningham
the documentation that comes along with many ports often seems like a heavy and arguably needless burden: - huge bloat - lots of often onerous, massive, fussy build deps - often takes as much time to sort out doc building as building the port and, the big one : I bet almost nobody ever looks