rvanlaar/djangorecipe — Issue #27: djangorecipe does not update scripts when there are new egg dependencies
Author: rvanlaar
Created: 2011-12-27 21:40:32+00:00
State: open
Labels: Fix Released, Undecided

Suppose you have a buildout.cfg like so:

[buildout]
parts = django
versions = versions

[django]
recipe = djangorecipe
version = 1.1
projectegg = myproject
eggs = my.egg.dep

[versions]
my.egg.dep = 1.2.3

When you first run buildout, the django script will have my.egg.dep-1.2.3 in it's path. If you change the buildout.cfg [versions] section to be "my.egg.dep = 1.2.5" and rerun buildout, the django script will continue to point to my.egg.dep-1.2.3 in it's path instead of the new version requirement of my.egg.dep-1.2.5.

The workaround for this bug is to delete the .installed.cfg file in the buildout directory before running buildout. This will force buildout to run the install method for all recipes.