Unusual working copy update requirements?

A little background:

I work for a startup & we have a few external contractors. I produce a
minimal distribution for their use in development, removing the
top-secret portions of the code that aren't necessary for their work. I
do my work on the full trunk & have a set of scripts that goes through
the source and removes anything marked as proprietary. I keep the
non-proprietary version in the repository as well - this allows me to
audit only those parts that have changed when I do a release.

My question is: how should I update my non-proprietary working copy?
I've been doing:

1. svn export full source
2. Run cleanup script
3. Manually copy (*not* with the svn client) on top of non-proprietary
working copy.
4. Audit diff of non-proprietary working copy.
5. Commit non-proprietary working copy.

This works ok, b/c the information about which files should be cleaned
is stored in separate files (I just moved off CVS - no properties). I'd
really like to convert my scripts to use svn properties. The problem is
then the export, since the property info is lost. What I'm unclear on
is how to update the nonproprietary working copy from a cleaned
full-source working copy, instead of an export.

My initial thought was to use svn update cleaned_full-wc
nonproprietary-wc, but won't that get confused b/c the working copies
come from different places in the repository? My other idea was to do a
regular cp and skip the .svn directories.

Now that you're thoroughly confused, any suggestions?

-- 
Peter Fein                 pfein@pobox.com                 773-575-0694
Basically, if you're not a utopianist, you're a schmuck. -J. Feldman
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org