Hello all, > So every time there is a change to the documentation, the repository > size goes up by the size of the file. Since everybody checks out the > whole repository, this affects everybody's disk space. I imagine > that compression gives us about 50% only. Roland, how much does > compression save? The uncompressed files are ~2MB compared to ~750kB compressed. Git will achieve the same compression (or more since it compresses the file itself and not streams inside) in its blobs. The pdf on disk will be larger. Pdf files (with text it in) are mostly made up of strings and ASCII representation of numbers so git will do a good job of generating diffs.
I generally agree that having the pdf files in the repo is awkward. I agree that for the reference guide we can expect users to generate it themselves. For the user guide this may not be quite as clear. If they want to look at the user guide to see how the build system (incl. the build system for the documentation works) then there is a chicken and egg problem. So if we remove UserGuide.pdf we should provide a plain text README file explaining how to build documentation, since this can be done even when no Cactus configuration builds successfully. Yours, Roland -- My email is as private as my paper mail. I therefore support encrypting and signing email messages. Get my PGP key from http://keys.gnupg.net.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Users mailing list [email protected] http://cactuscode.org/mailman/listinfo/users
