Re: Export a single different file?

> > [snip]
> > What's wrong with exporting and then deleting?
> > Anything else is going to be significantly more complicated.
> > [/snip]

> There are many ways of responding to this. Simply, only necessary files
> should get exported/accessed when an [automated] process is executed;
> with that said, an automated process should not go on a deletion spree
> (nor should it have such permissions).

> My objective is quite simple: have a repo of a WWW site, and have a
> dynamic export script. Depending on destination (dev/test/prod) any
> given set of files would get *excluded* from exportation. This would
> allow platform-specific configuration files to get equally versioned,

Can the automatated process determine which file(s) is(are) necessary?

If so, you could have the different versions of the config files in a
separate directory, or directories, in the repository and then either export
or cat the one(s) you want depending on the platform.

Admittedly, it's not as easy from your standpoint as an "--export-ignore"
option, but it should work with svn's existing functionality. As in, you
can use it now, instead of waiting for a feature to be implemented.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 19 18:04:56 2005