[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Exporting with externals doesn't work

From: Joachim Durchholz <jo_at_durchholz.org>
Date: 2007-11-21 11:37:46 CET

Ryan Schmidt schrieb:
> I believe the bug occurs any time you try to export from a working
> copy (regardless of what protocol you used to check the working copy
> out with), and I believe the bug does not occur if you try to export
> from a repository URL (again, regardless of the protocol). But I have
> not tested every protocol.

OK, I'll have to try it out.

Thinking about alternatives:

Since the script is doing a rollout, which means walking the directory
and munging files anyway: is an exported tree equivalent to a
checked-out repository with the .svn directories removed?
In that case, I could simply copy the repository tree and skip the
unwanted files (i.e. .svns and some other stuff that I'm currently
stripping after the export). This would also speed up the process
because the repository contains some large binary files that aren't
going into production anyway (test data and such).

Another alternative: wait for 1.5.
Should I hold my breath?


P.S.: Re CCing and reply-to headers: Thunderbird isn't smart enough to
properly react to mailing-list headers. I've been considering dropping
TB for a while now, it's just that I haven't come across a satisfactory
alternative yet...)

P.P.S.: I think that "export from the respository and have some file
munging" scenario is quite common. That's not really attractive though:
e.g. when rolling out for the customer, you don't want to first export
several megabytes of versioned test data just to delete them afterwards;
you'd want to filter them even before they get transmitted from the
repository to the rollout directory.
My knee-jerk reaction was "use a hook script then"; however, since every
hook script must serve all needs, this means that you have to coordinate
closely that the export will do something differently depending on
whether the checkout/export is for programming, for testing, or for
rollout. (In a larger organisation with separate teams for SVN
administration, programming, QS, and rollout, this is bound to become
even more painful.)
So how about *client-side* hook scripts? Have a parameter --hook-dir for
the SVN client. With a hook for checking whether a given file should be
exported at all, and a hook for munging the contents of a file (possibly
even before the file is written to disk: piping the file contents to
stdin of the hook script would suffice).

Just tossing around an idea and looking whether it's useful to anybody ;-)

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 21 11:43:33 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.