Thanks Robert,
It is a good idea and I might see if we can work with that. The problem is
that it is less flexible as it means we must have our staging area at the
same version as our production site at some point. This is rarely the case.
Frequently there will be a small part of the site that can go online now or
maybe even a few files that need to be brought up to date. The staging area
is in general far ahead of the production site and it is almost never all put
online simultaneously. I normally write a bunch of small cgi's for our
project managers to use so that I am out of the loop for site updates.. maybe
I can find some way of automating it using your idea but it is not as easy as
having some sort of "view" of the repository without the .fla's
I really appreciate your ideas, I am just trying to look for the perfect
solution... there must be other people who have this type of problem. Btw I
noticed that svn deals very nicely with branching compared with cvs.
Cheers
Alex
On Tuesday 09 March 2004 16:48, Robert Guthrie wrote:
> You could create a branch just before publishing your sites, then run a
> script that recursively finds your ".fla .psd" and other files and "svn
> rm"'s them from your branch. Then export that branch to your production
> sites.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 9 18:10:21 2004