If paver-minilib.zip is generated for different dependant packages with different paver version
then easy_install can fail.
I resolved this problem by downgrading paver to 1.0.3
By downgrading, you mean the paver you generated paver-minilib with?
Yes, I installed paver 1.0.3, then I regenerated paver-minilib in all projects, then I uploaded all packages to PyPI.
No more easy_install error.
OK, this should be fixed when new version is released then.
I will try to figure out how to release RC versions in such a way that they are available to easy_install on request, but not by default for new installs.
what about add paver version as a suffix to minilib filename (ie paver-minilib-1_0_5.zip)?
add version into minilib filename, fixes #46
@yedpodtrzitko IMO, this should be optional as it breaks backward compatibility.
@Almad what should be default status of this option, in your opinion? Buggy with warning message or backward-incompatible?
@yedpodtrzitko I'd go for buggy with deprecation warning when bad configuration is detected, as most people are using pip instead of easy_install those days, so I thing this bug is not so common.
make versioned minilib as an option (as well in setup generating), fix …
revert setup.py modification, fix #46