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

[Wouter van Heyst]

On Fri, Feb 13, 2009 at 10:55:20AM -0600, John Arbash Meinel wrote:

...

> 1) We need a way for the plugins to update the current state.
> 2) plugin/setup.py is not a good place for this, because setup.py is
> doing all sorts of things running as an interactive script.
> 3) I'm thinking that a function in plugin/__init__.py is also not the
> best place. It could work, but I sort of like having the setup code be
> fairly independent of actually loading a plugin.
> 
> From looking at the bzr setup.py code, we generally call a single
> function:
> 
> def get_qbzr_py2exe_info(includes, excludes, packages):
> 
> So what I would propose is to add a new file to plugins "bzr_setup.py".
> And have a single function in there called "get_py2exe_info(includes,
> excludes, packages)".
> 
> 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