Hello, I'm using the infrae.subversion recipe to collect various Products and packages from our subversion. The main goal here is, to not use svn:externals. But the buildout directive "develop=src/..." seems to have the requirement, that the packages are already present if bootstrap.py is called. So it is not possible to place packages there with buildout and get them picked up. 1. Is this correct? I searched and found others have the same problem. 2. What would be alternatives or how can this be changed? Thanks for answers and hints, __Janko Hauser
Janko Hauser, on 2008-01-27:
Hello, I'm using the infrae.subversion recipe to collect various Products and packages from our subversion. The main goal here is, to not use svn:externals. But the buildout directive "develop=src/..." seems to have the requirement, that the packages are already present if bootstrap.py is called. So it is not possible to place packages there with buildout and get them picked up.
1. Is this correct? I searched and found others have the same problem.
I see the same problem.
2. What would be alternatives or how can this be changed?
You can use the z3c.recipe.egg:editable recipe. I briefly tried that, but it did not work for our (Zest Software) internal password protected subversion repository, where we keep the code for our clients. The recipe tries to easy_install a package but it fails as it cannot use our repository without a password. In all other cases it should work though. I thought there was another problem that I saw with it. Ah yes, it throws errors when buildout is used in non-newest or in offline mode. I suspect this can be fixed, but I never reported it. Feel free to do so. Anyway, the following worked last time I tried it: ================================= [xm-development] recipe = z3c.recipe.egg:editable find-links = https://svn.plone.org/svn/collective/xm.booking/trunk#egg=xm.booking-dev https://svn.plone.org/svn/collective/xm.theme/trunk#egg=xm.theme-dev eggs = xm.booking xm.theme build-directory = src develop = true ================================= And then of course mention this section in buildout[parts] and add {xm-development}:eggs to [instance]eggs and perhaps [instance]zcml or wherever else you need them. -- Maurits van Rees | http://maurits.vanrees.org/ Work | http://zestsoftware.nl/ "This is your day, don't let them take it away." [Barlow Girl]
Maurits van Rees-3 wrote:
...
2. What would be alternatives or how can this be changed?
You can use the z3c.recipe.egg:editable recipe. I briefly tried that, but it did not work for our (Zest Software) internal password protected subversion repository, where we keep the code for our clients. The recipe tries to easy_install a package but it fails as it cannot use our repository without a password.
You can use the #egg trick within the [buildout] find-links variable, then add lovely.buildouthttp to take care of the svn login. You will need a simple .httpauth file in your HOME/.buildout directory ++ Tarek -- View this message in context: http://www.nabble.com/-buildout--bootstrap-and-develop-tp15119239p15309668.h... Sent from the Zope - General mailing list archive at Nabble.com.
Am 06.02.2008 um 19:07 schrieb Tarek Ziadé:
Maurits van Rees-3 wrote:
...
2. What would be alternatives or how can this be changed?
You can use the z3c.recipe.egg:editable recipe. I briefly tried that, but it did not work for our (Zest Software) internal password protected subversion repository, where we keep the code for our clients. The recipe tries to easy_install a package but it fails as it cannot use our repository without a password.
You can use the #egg trick within the [buildout] find-links variable, then add lovely.buildouthttp to take care of the svn login.
Thanks for yours and Maurits hints. I actually tried the recipe Maurits mentioned without success, but just yesterday an extension was published at pypi, which does exactly solves this problem. http://pypi.python.org/pypi/gp.svndevelop/0.1 Besides I didn't know that there is an extension mechanism besides recipes. One of our repositories is also password protected, but after the first successful login with an interactive svn session on the console this is not an actual issue. With regards and appreciation for the help __Janko Hauser
Janko Hauser-2 wrote:
Besides I didn't know that there is an extension mechanism besides recipes.
One of our repositories is also password protected, but after the first successful login with an interactive svn session on the console this is not an actual issue.
Yes that's how lovely.buildouthttp is hooked (a extension), to add authentication. So no interactive session is required at all. You should try it, it's very handy. For svndevelop, beware that your buildout syntax will therefore depend on this extension. Regular develop are fine, if you have a buildout-friendly layout in your subversion: you can checkout a whole tree and use relative paths in your buildout. ++ Tarek -- View this message in context: http://www.nabble.com/-buildout--bootstrap-and-develop-tp15119239p15324086.h... Sent from the Zope - General mailing list archive at Nabble.com.
participants (3)
-
Janko Hauser -
Maurits van Rees -
Tarek Ziadé