we use the following project structure:
- project-buildout (repos: svn.repository.com/customer/project/buildout)
- buildout.cfg
- src
- some.package (repos svn.repository.com/customer/project/package)
- another.package (repos another-svn-repos.com/some/path)
- git.package (repos git://...)
this setup is very common when using zc.buildout
(http://pypi.python.org/pypi/zc.buildout) together with mr.developer
(http://pypi.python.org/pypi/mr.developer)
typically you want to version-control the configuration files of your project
builout.
packages you develop on are checked out into the src folder from different
repositories.
in former subclipse versions i could simply
* check out the buildout (src folder has not been under version control)
svn co https://svn.repository.com/customer/project/buildout project-buildout
* check out some packages into src/ folder
cd project-buildout
mkdir src #(sometimes also src was under version control - both worked)
cd src
svn co https://svn.repository.com/customer/project/package some.package
* commit/update, add files to src/some.package using the subclipse ui
now the subversion related context menus are grayed out for those packages in
the src directory
a workaround is to put the src/ folder under version control and add all
packages as svn:externals
however, this is tedious and error prone since the checkout of these packages is
handeled by mr.developer
Description
Metadata Imported from Tigris (Issue 1465)