rdoc vs reprotest
In light of rdoc generated documentation making ruby packages fail
reprotest, I wonder whether shipping rdoc with ruby libraries is worth
the trouble of trying to fix this.
These docs are now easily available online and can be trivially rebuilt
from source by developers who need a local copy. They add a lot to the
size of the packages (e.g. of the 1.9M unpacked size of ruby-pg, 1.5M is
rdoc and 0.5M of that is standard boilerplate like JS, images, and
fonts), this in turn adds to archive size, network bandwidth, time it
takes to download and install the package.
Is dropping rdoc a reasonable tradeoff to fix reprotest?
If not, any ideas and/or volunteers for making rdoc generated
documentation reproducible and, ideally, less wasteful?
--
Dmitry Borodaenko
Reply to: