On Thu, May 7, 2015 at 1:18 PM, René J.V. <[email protected]> wrote:
> 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. > > 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? > +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)? -- brandon s allbery kf8nh sine nomine associates [email protected] [email protected] unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
