On Sat, May 23, 2009 at 8:17 PM, Eric MacAdie <e...@macadie.net> wrote: > I am looked a bit at the 407 page svn red book > (http://svnbook.red-bean.com/), and I might find an answer to this question > there, but I will ask here anyway. Can I exclude certain parts of the souce > directory tree from a checkout?
i'm don't know how > I ran "svn checkout http://svn.apache.org/repos/asf/james/ james" awhile > back, and it took about two hours to get all the source. The whole tree is > about 3.1 GB: > [er...@saigon][2009-05-21_21.30.13]$ pwd > /path/to/james-svn/2009-05-21_21.30.13 > [2009-05-23 11:51:13] > [er...@saigon][2009-05-21_21.30.13]$ perl ~/perl/getSize > The files in this directory add up to 3,395,115,127 bytes > 3315542.11621094 KB > 3237.83409786224 MB > 3.1619473611936 GB > [2009-05-23 12:14:28] WOW! i didn't know you could checkout such a big tree without infrastructure cutting you off > But there is a lot of old stuff in server/tags that I think I do not need: > [er...@saigon][tags]$ pwd > /path/to/james-svn/james-svn/2009-05-21_21.30.13/server/tags > [2009-05-23 13:55:05] > [er...@saigon][tags]$ perl ~/perl/getSize > The files in this directory add up to 1,202,976,544 bytes > 1174781.78125 KB > 1147.24783325195 MB > 1.12035921216011 GB > [2009-05-23 13:55:51] > [er...@saigon][tags]$ ls > build_2_1_1_fcs/ build_2_1_3_fcs/ build_2_2_0_fcs/ build_2_3_1/ > james_0_0/ JAMES-1_2/ > build_2_1_2_fcs/ build_2_1_fcs/ build_2_3_0/ deprecated/ > james_1_0/ JAMES-1_2_1/ > [2009-05-23 13:56:24] > > Is there an svn command that would allow me to get everything except the > server/tags tree? Having people download 1.1 GB of old stuff just seems like > a waste. once i explain some background, it might make a little more sense to you... apache james is a project: a self-organising community with a single set of committers developing the source and a single PMC with votes that bind apache. apache james server is the flagship product but most development now goes on in the libraries that compose the server. (one of the current debates is how far this process of componentisation should go.) each library is separately versioned and has it's own directory structure in subversion and subsite on the web. as you spotted, the downside of this approach is that it's tough to checkout the latest versions of everything together. http://svn.apache.org/repos/asf/james/protocols/current/ uses externals to do this for IMAP and 3.x. so - if people think it would be useful - i could easily create a 'current' which would checkout trunk for all 3.x components. not sure whether this would be a good idea or not. opinions? this process of componentisation happened mostly in the 3.x codestream. the 2.x code is monolithic (ATM). to checkout the stable server source, use http://svn.apache.org/repos/asf/james/server/branches/v2.3/ - robert --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
