[Grok-dev] Grok and eggs

[Kevin Teague]

> If there is another suitable alternative, please let us know.
>

A few other ways to make the libraries installed by a Grok app
available to another WSGI app:

1. Use collective.recipe.omelette to give you a flat view of the
Python libraries installed by a buildout-based Grok app. Put that
location on your PYTHONPATH.

I always add an omelette part to apps I'm developing anyways to give
me a flat, browsable view of the source code. Add the following to
your buildout:

[buildout]
parts = [the-usual-suspects] omelette

[omelette]
recipe = collective.recipe.omelette
eggs = ${app:eggs}

2. Convert version.cfg into the format readable by 'pip' and use that
to install the packages flat.

3. Install your other application using buildout :P

Buildout is a pretty nice tool. grokproject just creates a starting
buildout.cfg. It's perfectly reasonable to put other non-Grok or even
non-Python parts under control of a single install tool.