SVN - Can I skip files for targets I don't use?

[lee321987]

   Hey guys.  I'm using a dial-up modem, and it would be great if I could skip downloading files for players I never build for.  Is there a simple way to do it?

  Thanks in advance,

Will

[GodEater]

Not really no

[cool_walking_]

Perhaps .svn directories could be included in the source archives so that you would only need to download the ~18MB archive instead of doing a checkout.

[bluebrother]

svn mirrors your last checkout in the .svn folders. This means, if those are included in the tarball that would double it's size -- and getting a checkout isn't more than getting the sources themselves (the mirroring is done by the client and this is a feature of svn).

[cool_walking_]

getting a checkout isn't more than getting the sources themselves (the mirroring is done by the client and this is a feature of svn).

Doesn't it also include the state of the working copy? Meaning if the .svn folders are included in the archive, instead of a 400MB checkout, you can download a 35MB compressed archive and have a working working copy.

Or is there some way to tell SVN the state of an existing source tree that doesn't have any .svn folders (which would mean you could download one of the existing source archives and do the same thing)?

EDIT: And here's one I prepared earlier. http://www.mediafire.com/?z5szgitmdff

[Bagder]

1. The full 7zip Rockbox source package is currently 17.7MB

2. SVN sends data compressed over the wire, so the ~100 MB or so of files will be a lot smaller went sent. Not as much compressed as 7zip, but still. The very second you want to update your working copy you'll be happy you used svn since then you'll only get the necessary updates to transfer instead of a new 17.7 (or even larger by then) megabyte download.

[bluebrother]

getting a checkout isn't more than getting the sources themselves (the mirroring is done by the client and this is a feature of svn).

Doesn't it also include the state of the working copy? Meaning if the .svn folders are included in the archive, instead of a 400MB checkout, you can download a 35MB compressed archive and have a working working copy.

No. The state of the current working copy is saved to be able to send differences after the initial checkout, which makes updates much smaller -- you don't need to get anything again at all. As for an initial checkout that state is the same as your working copy will get there is no point in transferring it twice, so this isn't done.

And about your numbers, I just made a fresh checkout. According to TortoiseSVN 33.99MB were transferred -- even less than your 35MB archive including the .svn folders! An update is usually only a bunch of kilobytes for me.

[nls]

"svn help co" states that it supports a flag for turning off recursion (-N) so you should be able to check out only the dirs you want, the same flag is supported by "svn up"

[cool_walking_]

2. SVN sends data compressed over the wire, so the ~100 MB or so of files will be a lot smaller went sent.

Ah, I did not know that.

The very second you want to update your working copy you'll be happy you used svn since then you'll only get the necessary updates to transfer instead of a new 17.7 (or even larger by then) megabyte download.

I wasn't saying to do this every time, but just once instead of "svn co", so that you can from then on use "svn up".

And about your numbers

I think some un-befuddling is in order:
18MB = Approximation of the current Rockbox sources .7z archive. Before I actually compressed it, I assumed this would ballon up a bit because of the .svn folders, but I hoped that since most of the content of the .svn folders is a copy of the source text, it would only go to 20MB or so, not enough for me to bother to change the written number to 20, and I hadn't actually done it yet so I didn't want to write some speculated number.
35MB = Size of archive with included .svn folders.
400MB = Was supposed to be the size of the uncompressed Rockbox sources.  As I was writing my previous post, I tentatively wrote 400MB (I think I saw this number on the mailing list somewhere, though 200MB was also rattling around in my head) with the intention of checking it, and forgot to check it.