The problem is that when I run buildout, I keep getting the error Directory name for existing package 'mytheme' differs. Expected '/plone/instance/mytheme/src'
I've tried different permutations of invoking buildout and mr.bob but none of them seem to get me past that error. What am I doing wrong?
I managed to get past one of the errors by changing my buildout file to add directories to the "develop" buildout item. Unfortunately, now I'm getting the error No such file or directory: /plone/addon/theme/mytheme/src/setup.py. The setup file is in /plone/addon/theme/mytheme. How do I make mr.developer look for that file in the right place?
My buildout configuration now looks like this (I moved the addon's path too):
Wouldn't that remove the addon that I'm trying to build, though? I've already confirmed that the buildout works without attempting to install the addon.
My approach of developing a customer addon is to setup a deployment plone buildout and develop my addon in the src/ folder. This then looks something like this:
with this approach you can simply add other addons in the [sources] section and add them either to your setup.py install_requires or your [instance] eggs ...
Check out the mr.developer documentation. You can set the branch you want for working on a feature branch of the source checkout on a feature branch of the deployment (and turtles all the way down, if working on a nested policy).
When I finally gave in and put the project in git, I made it past the error. I guess I just couldn't figure out how to get addon development working with the filesystem.