This is not needed for now.

This is just a initial skel with code based on erp5 setup.

- a list of repositories to synchronize can be provided
- the first repository is used for software
- transfer project revision with string like
  [repo x]=[commit count x]-[hash x],[repo y]=[commit count y][hash y]
- change related to new structure :
  recipe slapos.recipe.erp5testnode is inside slapos.cookbook egg
- allow authentification setting for several repositories
- drop support for svn

http://svn.haxx.se/dev/archive-2011-06/0030.shtml

Development Install the latest version directly from git repository.
This will possible become the standard way to install cloudooo.

Reorganise cloudooo component and stack to reuse code instead duplicate it.

Follow the rules. Do not add new things into 'master' branch, but use
slapos one. It was used to introduce slapos component, and as repository
is about slapos, this place seems the best way to start explaining.

Thanks to using own python with own libraries, there will be library version
conflicts, as lxml is built against own libz.

Thanks to using own python with own libraries, there will be library version
conflicts, as lxml is built against own libz.