[Development] Making docs being built for every module
Thiago Macieira
thiago.macieira at intel.com
Thu Jun 6 17:58:53 CEST 2013
On quinta-feira, 6 de junho de 2013 17.57.08, Oswald Buddenhagen wrote:
> for the packagers, it would be the best solution to simply include the
> docs directly into the particular source tarballs. we have been doing
> that in ancient times. and its consistent with shipping the syncqt'd
> headers, and configure.exe, even if for somewhat different reasons (the
> general theme being "simplicity for the user").
Right.
The drawback is a major increase in the size of those tarballs.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20130606/42813981/attachment.sig>
More information about the Development
mailing list