On 9 Dec 2014, at 15:30, Frank Loeffler <[email protected]> wrote: > On Tue, Dec 09, 2014 at 03:12:25PM +0100, Ian Hinder wrote: >> 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. > > Yes, this is an unfortunate side-effect of first of all storing this in > a VCS in the first place, but also of using a system that stores the > whole history locally. Maybe we should take this as opportunity to think > again about whether we should put these generated files in the VCS in > the first place. They don't really belong there. > > The intention is that a user has the documentation quickly and easily > available. If we would, say, find a way to have the documentation online > updated automatically, I would say we wouldn't need to provide the pdfs > in git anymore. It is probably save to assume that any user has some > kind of Internet connection - not all the time, but most of it. We could > even get the pdfs of a release from within the thornlist from such a > website.
And if they are offline, *and* need the documentation, they just have to run the make command to build it. See https://trac.einsteintoolkit.org/ticket/1039, from 2 years ago. As mentioned in that ticket, I would like a user on the website SVN server specifically for automated systems to update the website, without having to store the password of a CCT system account in plaintext on an automated system. -- Ian Hinder http://numrel.aei.mpg.de/people/hinder
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Users mailing list [email protected] http://cactuscode.org/mailman/listinfo/users
