-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
P.J. Eby ha scritto:
At 10:39 PM 5/22/2010 +0200, Manlio Perillo wrote:
The trivial solution is of course to not use "develop" command, and to build a normal egg.
Right. The slightly-less-trivial version is to make sure your source is in subversion, and add svn: links to your --find-links.
Unfortunately I no more use Subversion. Do you plan to add full support to other VCS, or should I switch to a setuptools fork?
If `-maxd` will make the B.egg-info file relative, then all I need to do is to `python setup.py develop` inside A directory, and B package should be correctly available.
Is this possible?
The -a in -maxd means that you must have either a source distribution (e.g. an sdist .tgz, svn: link, etc.) or an .egg. It cannot do .egg-info at the moment (although when it grows PEP 376 support in 0.7 it probably will).
Is it .egg-info or .egg-link ?
If it is an .egg-link, then this could be copied as with normal eggs, of course promising (to setuptools) that the path is linked to a valid directory.
I tried right now, and it is possible to specify a relative path in the .egg-link file.
Btw, there's still one MORE way to do this:
easy_install -maxd targetdir sourcedir1 sourcedir2 ...
Where sourcedir1, sourcedir2, etc. are local paths to project directories containing setup.py files. They'll all be built eggs and put in the targetdir.
(If you do this, however, you should list the dependencies *first*, rather than last, otherwise it will not be able to resolve them, if you are still only using 'develop' installs there.)
What do you mean by "first"?