<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, May 7, 2015 at 1:18 PM, René J.V. <span dir="ltr"><<a href="mailto:rjvbertin@gmail.com" target="_blank">rjvbertin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I thought it'd be nice to have the kdelibs4 documentation in Qt help (.qch) format. It is available online, but seriously outdated and will of course not reflect any OS X specific changes that we made.<br>
<br>
There is a script in the doc/api directory that generates this documentation file, but it hogs the computer for over an hour. My initial thought had been to generate it unconditionally if the user selects the +docs variant, but not when there is so much overhead. What alternatives are there? I could create a subport, but that would still cause this documentation to be rebuilt each time an update is pushed and the user does an `upgrade outdated`, which seems overkill to me. If it were just me I'd let the generation depend on the presence of a specific env. variable, in the +docs variant; would that be acceptable?<br></blockquote><div><br></div><div>+docsfull variant? Perhaps with some way in the Portfile to specify that an update should rebuild it only if there is an installed version older than some threshold (and maybe a +docsfullalways variant for those who want it to always build for some reason)?</div></div><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div><div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div></div>
</div></div>