RE: trunk/branches/tags and projects w/components

>In my case, I have the trunk/branch/tag under each project directory

Like I said, I can argue either way, but the downside I see of that
structure is that I can branch a project and compile it. But I could
then take the compiled .dll and .aspx and put it into the trunk of /site
and have the trunk of /site using a branched .dll -- and have no way of
tracking that.

>so I can easily control access to each project.
You should be able to control access anyway, no? authz works inside the
/trunk, branch, tag structure, doesn't it?

I guess the problem is, I can pick on now, and make it work. But I'm
concerned that in 12 months I'll go "if only..." when I come across some
good reason I shouldn't have done it that way.

-Walden

--
Walden H Leverich III
Tech Software
(516) 627-3800 x3051
WaldenL@TechSoftInc.com
http://www.TechSoftInc.com
Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org