devyan parmar, on 2009-12-18: > > Hi, > > I am using buildout for my project development as well as for deployment. > which makes process easy and help in repeatability. > but facing one problem while choosing particular versions of eggs while > running buildout. > i have eggified my python packages and releasing version wise. > i have created "versions.cfg" where i mentioned all my project related > packages with proper version. > it's working fine for latest eggs version. but if i wants to choose older > version egg from my package server, It takes latest only. > even after specifying in versions.cfg also. > > following attributes am using in my buildout.cfg > > [buildout] > newest = false > prefer-final = true > allow-picked-versions = true > extends = version.cfg > preferences.cfg > versions = versions > > to avoid this i am deleting existing packages from my eggs folder and > rerunning buildout. > > Please suggest me here...
I do not see this behaviour. I tried this buildout.cfg: ============================== [buildout] newest = false prefer-final = true allow-picked-versions = true versions = versions parts = virtualenv [versions] zc.buildout = 1.4.3 virtualenv = 1.4.2 zc.recipe.egg = 1.2.2 [virtualenv] recipe = zc.recipe.egg:scripts ============================== If I lower any of the versions, that change gets picked up by the next bin/buildout run. You may need to run buildout once in newest mode on the command line: 'bin/buildout -n'. At least, I sometimes seem to need that when buildout has previously already gotten some version of a package and apparently sometimes does not realize that the required version has changed. Newest mode here effectively says: yes, buildout is allowed to get other versions. -- Maurits van Rees | http://maurits.vanrees.org/ Work | http://zestsoftware.nl/ "This is your day, don't let them take it away." [Barlow Girl] _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
