Importing existing applications
The svn import command is designed to place a directory (and its subdirectories)
under version control. Unfortunately, it is only an import, not a checkout. It does
not turn the imported directory into a working copy, which is usually the behavior
you want when importing a project that is already under development.
Trac Python, Subversion Great Subversion integration. Very nice workflow. Based on modular
architecture, so many plugins are available. However, it can
be difficult to install. Currently used to manage Rails development
(http://dev.rubyonrails.org/).
Lighthouse Rails (Hosted) New subscription-based issue-tracking service by Active Reload
(Rick Olson and Justin Palmer). Very slick interface, good extensibility,
and integration with email.
Product Platform Description
310 | Chapter 10: Large Projects
There is a neat Subversion trick to add an existing directory tree ???in place??? to an
empty repository. You can use this when putting an existing application under version
control:
$ svn mkdir svn://repo/my_app/trunk
$ cd my_app
$ svn co svn://repo/my_app/trunk .
$ svn add *
$ svn ci
To add only certain directories without their contents, pass the -N (--non-recursive)
flag to svn add. This is very useful when setting contents of certain directories to be
ignored; for example, these commands will add the public/attachments directory
while ignoring its contents:
$ svn add -N public
$ svn add -N public/attachments
$ svn propset svn:ignore "*" public/attachments
Subversion Externals and Piston
Subversion has an externals facility for pulling in code from other repositories.
Pages:
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472