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

project creation within trac...

From: bruce <bedouglas_at_earthlink.net>
Date: 2005-04-14 16:31:20 CEST

hi...

can't get to the redbook right now.. so i'm doing this from memory. bear
with me.

i'm looking at using SVN under Gforge/ViewCVS. however, these apps only
appear to allow you to setup the top level project, and/or allow you to view
the project after it's been setup. the apps appear to leave it to the admin
to create the underlying project/directory layout.

here's my question. regarding a project directory layout, do people use a
'standard' directory structure for the projects under their SVN repository?
this would seem to make the process of setting up a SVN repository for a
given project straightforward...

here's what i imagine the basic steps to be for setting up a repeatable SVN
project creation process

1 - create a standard project directory layout on your hard drive. store
this in foo
    foo
      -branches
      -tags
      -trunk
        -docs
        -test
        -bin
        -build
        -utils
        -data
        -examples
        -config

    foo2
      -branches
      -tags
      -trunk
        -docs
        -test
        -bin
        -build
        -utils
        -data
        -examples
        -config
        -images
        -database

    etc....

2) create the svn project
    svnadmin create svn://foo/svndir/svn_projectname

3) create working copy for project name
    mkdir /svndir/wc_projectname
    cp -r foo /svndir/wc_projectname
    svn import /svndir/wc_projectname svn://foo/svndir/svn_projectname
    svn update
    svn commit
    rm -rf /svndir/wc_projectname
    svn co svn://foo/svndir/svn_projectname /svndir/wc_projectname

this process gets us a project/dir layout that could work, and this could be
automated easily enough..

are there any issues with this approach? is this the basic approach that
others go through?

also, if i wanted to be able to determine when a file has been checked
in/out, is there a way to do with SVN? or, would i have to capture this some
other way? any ideas/suggestions as to how i might do this?

how does SVN keep track of who has which files in/out? or does it? am i the
only one with these questions????

i'm looking ahead to when a mgr might want to say, give me a report on how
many files are checked out by john/whoever...

also, SVN has TortiseSVN for windows. are there any other linux based SVN
GUI client apps that are good...?

as far as allowing users interaction with the underlying SVN project
repositories, here's what i'm thinking:
  -allow the user to create/manage the project via the Gforge/Trac/Etc...
app
  -allow the user to interact with the SVN project repository via an SVN
client.
   (This requires the user to login to SVN, which then directs him/her to
the
    correct project, based on SVN/HTTP/System authentication)
    -How will the working copy on the local system be handled?
    -Will the user have to create a duplicate of the entire project
directory
     structure, or simply setup some type of working copy/directory for
     the files that the user is modifying...????
    -Should the user be given some tool, to create the entire project
directory
     layout on the local system/machine? this would allow everyone on the
     project to rebuild in a consistent manner if needed...

  -still need a way to determine the checked (in/out) status of the given
   project files....

thoughts/comments/ideas/etc...

thanks

bruce

Bruce Douglas
(925) 249-1844
(925) 846-1062 (h)
bedouglas@earthlink.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 14 16:34:30 2005

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

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