[RFC] Spec for having plugins bundle their dependencies into installer

John Arbash Meinel john at arbash-meinel.com
Fri Feb 13 17:04:27 GMT 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


...

>> So then bzr's setup.py could do:
>>
>> for plugin in plugins:
>>   if os.path.isdir(plugin + '/bzr_setup.py'):
>>     import ...
>>     bzr_setup.get_py2exe_info(includes, excludes, packages)
> 
> What does this get_py2exe_info give you? Dependencies seems like
> something eggs should handle, however much I dislike them.
> 
> Wouter

We need to tell py2exe what dependencies we need. At the moment for
bzr-svn this just does:
  packages.append('subvertpy')

I'm not sure what info is contained in eggs, though I know that we do:

 python bzr-svn/setup.py install -O1 --install-lib=RELEASE_DIR

so I believe the .egg files are generated. They are generated fairly far
apart from 'bzrlib/plugins/svn/*' though (I believe they show up in the
root dir).

Also, I believe the egg files have the version number in their name, so
you would probably need to teach py2exe to read all of the
RELEASE_DIR/*.egg files and include whatever dependencies show up there.

Oh, and you probably don't have a way to say "Don't include
PyQt4.elementtree.ElementTree" as part of egg files, so we still need
something to do that sort of work.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkmVqBsACgkQJdeBCYSNAAPWcACfeLAycIfRRg7htcVjDMGYMdbn
RfIAnisu3HPMPBATPxT+ZwUQvUkXOt6u
=0MOa
-----END PGP SIGNATURE-----



More information about the bazaar mailing list