On 11/3/2005 1:21 PM, Anastasios Angelidis wrote:
> This is some questions in general I'm hoping some of you can answer...
>
> Where I come from we do all versioning by hand and have come acustomed
> to certain procedures that we have implemented. I'm currently looking at
> implementing subversion for our version control and would like to see
> how I can integrate svn with out processes to possibly remove some of
> the manual work.
>
> 1- We have the following structure: Builds -> Projects -> Components ->
> Elements
>
> Build: Contains multiple projects
> Project: Contains multiple components (Executables, Dbs, Web etc...)
> Component: Contains multiple elements (source files etc...)
>
> We have a custom in house to that we track versions like 4.3.5 in a sql DB.
>
> 1- Would I be able to track version numbers through svn, without having
> to rely on the sql db?
Yes, it's very easy to record the version of every file in a collection
by making a copy of the collection to a tag directory. (You don't
actually make any physical copy, just a logical copy.)
> 2- What would be the best way to handle a "build" as described above. As
> using 3 levels in a directory treet structure is cumbersome.
There'd be no need to change your current directory structure. Just
import it into subversion and call it the trunk.
Duncan Murdoch
>
> Thanks
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 3 19:33:54 2005