At 12:41 AM 5/23/2010 +0200, Manlio Perillo wrote:
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?
As I mentioned, support for URL prefix plugins will be added in
0.7. (Not necessarily in the first alpha though.)
>> 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 ?
First off, there really isn't any sane meaning of 'develop' in the
context of a -maxd tarball. A -maxd tarball needs .egg files or
directories, or else you should just use pip to build a bundle or
whatever it's called in pip.
What do you mean by "first"?
I mean, "easy_install -maxd targetdir dependencysource
dependersource" - the dependency source directories are to be listed
before the source directories that depend on them.
All things considered, this is probably the easiest way for you to
build a tarball-deployable directory from local source packages that
are not indexed on PyPI or pre-built.
(I don't know whether pip can handle this use case; i.e., I don't
know if it will take source directories as arguments.)
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
