user manuals
Jeremy Lavergne
jeremy at lavergne.gotdns.org
Tue Mar 5 06:14:30 PST 2013
It's probably better to create subports that install documentation only.
The original reason these were left off were
* slowing down an already humongous build cycle (no longer an issue thanks to buildbots)
* doc building used meinproc4, which routinely crashed and prevented installation (might still be a problem)
On Mar 5, 2013, at 12:01 AM, Ian Wadham wrote:
> 4. Many KDE apps come with user manuals: should MacPorts install them by default?
>
> If no, I will add a recommendation to the Wiki to use the +docs variant. If yes,
> is there perhaps some more efficient way for Macports to provide them?
>
> I am unclear on what variants do exactly (ie. local vs. global). If I ask for +docs,
> do I get it on all the dependencies?
>
> Also, with +docs I seem to get all the dependencies needed to generate every
> possible format of the application's API doco from Doxygen (not required by the
> average user). KDE user manuals are in XML and follow the Docbook convention
> and there is a KDE utility to convert them to HTML during build and installation.
More information about the macports-dev
mailing list