On May 7, 2015, at 10:18 AM, René J.V. Bertin <[email protected]> wrote:
> Hi, > > 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? Due to license conflicts the MacPorts kdelibs4 port is not binary distributable, but, if the license for the docs is friendly a subport could avoid the time required for doc generation when there is a buildbot for the users platform and the user has the default prefix. Regards, Bradley Giesbrecht (pixilla)
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
