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

Re: ClearCase-like repo structure (Was: Accessing different revs via Apache?)

From: Noel Yap <yap_noel_at_yahoo.com>
Date: 2002-10-09 21:17:22 CEST

--- Peter Davis <peter@pdavis.cx> wrote:
> On Wednesday 09 October 2002 11:13, you wrote:
> > 3. Will the post-commit trigger execute all
> commands
> > that I may care about (eg mkdir, import)?
>
> I think the only thing you'd want to do is copy and
> possibly mkdir. The
> post-commit doesn't have a working copy, so there
> would be no import.

I think I misposted my question. It should've been:
Will the post-commit trigger execute for all commands
that I may care about (eg mkdir, cp, import)? Upon
import, the trigger should create the necessary LATEST
and 0 branch and label, respectively.

The trigger shouldn't need a working directory since
all it's doing is directly creating copies in the
repository. Or am I missing something?

> > Also, I still need to think about an efficient way
> to
> > figure out the next per-branch revision number.
> Maybe
> > I can make it or the current LATEST revision an
> > attribute (oops, I mean property ;-) of the
> branch?
>
> This is related to possible locking issues. If you
> don't have a lock
> surrounding when you check the property and when you
> create the directory,
> then that will definitely cause problems. Maybe
> Subversion has that problem
> solved already?

I'll double check the docs to see how triggers
interact with the transactions. Since Subversion is
using a database, I'd think things should work as
expected (eg a transaction can't lock itself out and
everything occurs within the same transaction), but
you never know.

> I was just trying to demonstrate that there isn't
> really a connection between
> the labels and actual revisions. The post-commit
> script will create a new
> revision for each copy in addition to the original
> commit, so in real life
> the revision numbers of the labels would increase by
> two every time, in
> addition to increases do to branch commits.

I hadn't thought of this (that the repository revision
increments for each branch/label created) but it
shouldn't really matter, anyway.

Thanks,
Noel

__________________________________________________
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 9 21:18:23 2002

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

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