For reference,
235M kdelibs-apidocs-4.7.4-1.fc16.noarch.rpm
So, in an effort to make releng/infra/mirrors happier, I was looking into
the possibility of packaging pregenerated content from http://api.kde.org/,
rather than respinning kdelibs-apidocs on every kdelibs pkg build.
So, here's my general take (please correct or confirm where appropriate):
* These -apidocs are generated via doxygen from lgpl sources, so, lgpl
applies to -apidocs
* what source code requirements are there? is the -apidocs 'preferred form'
of the source... the kdelibs source code? or is the pregenerated html docs
themselves good enough?
if we need matching kdelibs source code, then...
One issue raised is that api.kde.org generates their content daily from scm
branches, which likely doesn't match exactly the sources that we distribute
(say in our kdelibs.src.rpm's). In case we'd try to take scm source
snapshots to satisfy source requirements, it not clear (at the moment
anyway), which exactly branch/commits are used by upstream either.
So, how picky do we need to be, if at all, about satisfying lgpl source
requirements to pursue trying to package pregenerated lgpl documentation
from api.kde.org ?
-- rex
