For the community, if you want to get the source, there is a public access to the repository.
$> mkdir projects
$> cd projects
Get a clone of each repository
$> bzr clone lp:~openerp/openobject-server/trunk server
$> bzr clone lp:~openerp/openobject-client/trunk client
$> bzr clone lp:~openerp/openobject-client-web/trunk client-web
$> bzr clone lp:~openerp/openobject-addons/trunk addons
Link the addons to the server
$> ln -s addons/* server/bin/addons
If you want to get a clone of the extra-addons repository, you can execute this command
$> bzr clone lp:~openerp-commiter/openobject-addons/trunk-extra-addons extra-addons
Cool, you have the last version of the trunk !
For more information, see the wiki page: HowToContribute
Posts
4 comments:
With the latest trunk, there is no need to put addons under the `bin` directory. Now you can put addons separate. Start OpenERP server like this:
$ ./tinyerp-server.py --addons-path=/path/to/my/addons
The `bin/addons` will be considered as default addons directory which can be overriden by the `/path/to/my/addons/'. That is if an addon exists in `bin/addons` as well as `/path/to/my/addons` (custom path) the later one will be given preference over the `bin/addons` (default path).
Would this fix some of the errors i am running in to? and would you be able to have one-on-one chat with me about OpenERP?
You can use the forum of OpenERP if you have a question !
... Then update your local branches by running
$> bzr pull
in the each project directory.
Post a Comment