Op Ma, 2010-05-10 om 10:05 +0200 skryf Hedley Roos: > Hi > > I've been able to successfully avoid this problem for a while now, but > with Plone 4 looming I have to face it. > > The issue is with dependencies explicitly listed in an egg's setup.py. > As an example PloneSoftwareCenter lists Products.ArchAddOn. Not > Products.ArchAddOn<=1.5 etc but just the egg name. > > The PloneSoftwareCenter release is 1.5.5 which is still compatible with > Plone 3, but ArchAddOn now has an 1.6 as the latest release. That > version tries to pull in Plone>=4.0dev. > > Attempting to pin ArchAddOn to 1.5 in buildout.cfg is futile since the > setup.py file seems to always win. > > Does anyone know how to force version 1.5? And what is the best practice > for setup.py files? Should you specify a version range or not?
This shouldn't be a problem. We specify setup.py egg dependencies in our policy egg, and then pin them in a versions.cfg file. Not having a version specified in the setup.py shouldn't mean that the newest version is fetched and that versions.cfg is ignored. JC -- http://opkode.net _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
