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

RE: Re: concerning repository storage type

From: Bicking, David (HHoldings, IT) <David.Bicking_at_thehartford.com>
Date: 2007-10-22 15:43:26 CEST

> -----Original Message-----
> From: Andy Levy [mailto:andy.levy@gmail.com]
> On 10/22/07, nav@ciklum.net <nav@ciklum.net> wrote:
> > Thanks!
> > But here is one more question:
> >
> > there are actually several sites we're going to work on, and these
> > sites use some common components.
> > Website1 = Solution1 = Project1 + Project2
> > Website2 = Solution 2 = Project3 + Project2
> >


> Symlinks don't work on Windows, so that might pose a problem.
> Use svn:externals to pull Project2 into the other projects.
> svnlook changed in your post-commit will show you what's been changed.
> Parse the paths and take the appropriate action based on
> what's changed.

> SVN looks for .bat, .cmd and .exe files when executing hooks.
> Do you really want to do an export each time? Depending upon
> the size of the project, that could take a while. Make each
> site under wwwroot a working copy, then you can update with a
> much-faster svn update.

For development, I'd do what you suggest, Andy. When it comes time for
"production deployment", I'd have some kind of managable process. Also,
for ASP.NET projects, I set a virtual folder that points to my workspace
(per Microsoft's best practices). This ensures that all the source goes
into the same place on the local drive.

I'm building a pre-commit "script" in C# as a DLL project, and calling
it from a BAT file. This works well, though I'd rather be learning
Python ;)

If your company is willing to permit the software, Perl and Python both
work in Windows, so some of the scripts are therefore cross-platform.

This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information.  If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited.  If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 22 15:43:51 2007

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