ENHANCEMENT: Add "--non-recursive" flag for export

["Rowell, Geoff" <gr...@ENVOYWW.COM>]

Really could have used this feature recently when developing packaging
scripts. I didn't see an issue that applies to "svn export".
 
I'd like to be able to export a single directory, without any
housekeeping information. And, I'd like the "--non-recursive" flag to be
transient - if I export again to the same destination without the flag,
I'd expect it to default to the standard recursive behavior.
 
Thanks,
 
Geoff Rowell
Quality Assurance
EnvoyWorldWide, Inc.
781.482.2125
www.envoyworldwide.com <http://www.envoyworldwide.com/> 
 
Communicate. Transact. Succeed.

Re: ENHANCEMENT: Add "--non-recursive" flag for export

[kf...@collab.net]

"Rowell, Geoff" <gr...@ENVOYWW.COM> writes:
> Really could have used this feature recently when developing packaging
> scripts. I didn't see an issue that applies to "svn export".
>  
> I'd like to be able to export a single directory, without any
> housekeeping information. And, I'd like the "--non-recursive" flag to be
> transient - if I export again to the same destination without the flag,
> I'd expect it to default to the standard recursive behavior.

This is complex.

In checkouts, it is our long-term goal to make non-recursivity
"sticky", that is, a property about the working copy that the working
copy itself remembers, and can apply to subsequent commands.

But for exports, there would be nowhere to store that that stickiness,
because exported trees store no metadata at all.  In other words,
exporting over an existing, previously-exported tree (whether
non-recursive or not) is no different from exporting over some random
directory tree unrelated to the repository in anyway.  Whatever
behavior the latter gives you, the former ought to as well.

So, does it not do this currently?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org