geremyk / google-gdata

Automatically exported from code.google.com/p/google-gdata
0 stars 0 forks source link

Move generated content out of trunk #153

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Generated content should be moved out of the SVN trunk.

Out of the 206 MB stored in trunk, 157M of this is stored in 
trunk/clients/cs/docs/generated. This 
is a lot of data to download when checking out a new working copy of the 
repository, all of which 
could be re-generated on the client after downloading.

Not to mention all of this information can be accessed online.

Original issue reported on code.google.com by tjohns.ggl.legacy@gmail.com on 28 Jul 2008 at 4:30

GoogleCodeExporter commented 8 years ago
This information can only be accessed online because it is part of the trunk :) 
I might move it a different 
repository though. It's just a bunch of work/time. 

Regenerating, while possible, is non trivial (install sandcastle, wait 
30minutes to build etc), so i do not think 
that is a good option. 

I think the best option is to move the documentation into a seperate project.

Thanks for the suggestion.

Frank Mantek

Original comment by fman...@gmail.com on 28 Jul 2008 at 9:27

GoogleCodeExporter commented 8 years ago
It doesn't have to be in trunk to be available online, it just has to be 
somewhere in SVN. You could break the 
repository up into trunk/tags/branches/generated, for example.

And ya, I definitely agree that regenerating this stuff from scratch is a pain, 
but if somebody takes the time to 
download the code from SVN, they're probably willing to take the time to 
install the rest of the dependencies. It 
would definitely make sense for the standalone downloads could still have the 
generated content in them, 
though.

Original comment by tjohns.ggl.legacy@gmail.com on 29 Jul 2008 at 8:11

GoogleCodeExporter commented 8 years ago
moved it to /docs in the root of the repository

Original comment by fman...@gmail.com on 31 Jul 2008 at 3:50