<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Ken,<div class=""><br class=""></div><div class=""><br class=""></div><div class="">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. </div><div class=""><br class=""></div><div class="">See <a href="https://trac.macports.org/ticket/58338" class="">https://trac.macports.org/ticket/58338</a>. </div><div class=""><br class=""></div><div class="">I propose “docs” for a variant name and “-docs” for the sub-port name addition. </div><div class=""><br class=""></div><div class="">I agree that, in general, the documentation should not be installed by default. Based on what Josh said, we don’t need to make it a rule, just a recommendation. If we unify the variant name, people can at least set “-docs” in their variants.conf file. </div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Cheers!</div><div class="">Frank<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Sep 19, 2019, at 10:40 PM, Ken Cunningham <<a href="mailto:ken.cunningham.webuse@gmail.com" class="">ken.cunningham.webuse@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">the documentation that comes along with many ports often seems like a heavy and arguably needless burden:<br class=""><br class="">- huge bloat<br class="">- lots of often onerous, massive, fussy build deps<br class="">- often takes as much time to sort out doc building as building the port<br class=""><br class="">and, the big one :<br class=""><br class="">I bet almost nobody ever looks at them, much less uses them. <br class=""></div></div></blockquote></div><br class=""></div></body></html>