RE: Re: Query: svn externals and export

> On Dec 10, 2009, at 03:14, Andrew Hardy wrote:
>
> > On Dec 9, 2009, at 12:34, Ryan Schmidt wrote:
>
> >

> > I was hoping to avoid performing a checkout as this would create all the .svn directories, etc.
>
> Yes it would, if by "etc." you mean the contents of the .svn directories.
>
> > and effectively double the data downloaded.
>
> There is no difference in the amount of data downloaded from the repository server to the client between the checkout and export command. The difference is that the checkout command makes a second copy of the files on the client, and adds additional administrative data, in the .svn directories. So the only "problem" with a checked out working copy is the extra disk space it takes on the client; you'll have to compare the disk space available with the size of your project to know if this is going to be a problem.

It's more an issue of the time it takes to bring down the data, which can have an impact on some of the users.

> The advantage of the working copy is that you can update it to the latest version simply, and only the differences are transferred over the wire, whereas if you only had an export, you'd have to export the whole thing again to get the updated version.

I'm trying to avoid builds occurring from a WC. In general, the users here will only have a single WC for the project and they will tend to have 'extra' files in their WC that hasn't been committed. By building from their WC, we cannot be sure that the build is reproducible solely from the repository. In addition, we 'package' the build directory for delivery and I don't want it to include information that should not be delivered to the end-user e.g. documentation.

> There's no reason you couldn't directly use repository URLs to read the svn:externals properties.

The main reasons for this is that my Windows command script skills are somewhat lacking!

>They're both messy, the way you want to have it.

Probably! Is it normal practice to build 'releases' from someone's WC? I'm not sure whether it helps for understanding, but our build doesn't result in the production of a single executable - we're producing database creation scripts, code to be installed into the database, code to be run against the database, etc. and a further script to orchestrate this.

Anyway, the 'export to temporary and move to build' approach seems to be working... at the moment... It sounds like this is not the 'standard' way of doing things, so I should probably investigate what others do in this situation.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2429166

Please start new threads on the <users_at_subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <users-subscribe_at_subversion.apache.org>.
Received on 2009-12-10 12:47:09 CET