[Development] Making docs being built for every module

Lisandro Damián Nicanor Pérez Meyer perezmeyer at gmail.com
Thu Jun 6 18:07:06 CEST 2013

On Thursday 06 June 2013 08:58:53 Thiago Macieira wrote:
> 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.

And some of us would be required to re generate in order to asset that we can 
build it from source, so it wouldn't help a lot.

Once again, this is our specific case, some other may benefit from this.


Lisandro Damián Nicanor Pérez Meyer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20130606/bab66484/attachment.sig>

More information about the Development mailing list