Adding ZopeSkel to a Buildout

UPDATE I thought this was broken, but I think it was just my convoluted setup. If you try this, please leave a comment and let me know how it went for you!

A quick note, if you want to add zopeskel to your development buildout.

All there is to it is to add the following part to your buildout.cfg:

[zopeskel]
recipe = zc.recipe.egg:scripts

eggs = PasteDeploy
       PasteScript
       ZopeSkel

scripts = zopeskel
          paster

Then just enable it by adding zopeskel to the parts parameter of your main [buildout] section.

[buildout]
     parts = zopeskel

When you re-run bin/buildout, buildout will grab the necessary packages, and create a paster and zopeskel script in your bin directory.

Note: I wanted the paster command, since I’m used to ZopeSkel’s “standard” user interface.  To get this, I had to add the PasteDeploy egg and paster script to the configuration. Feel free to omit it if you just want to use the new “kinder, gentler” interface. I haven’t tried it yet, but I believe the explicit inclusion of the PasteScript egg is unnecessary.

Advertisements
This entry was posted in Uncategorized. Bookmark the permalink.

One Response to Adding ZopeSkel to a Buildout

  1. You can use
    dependent-scripts = true
    to generate scripts for all required eggs in addition to the eggs specifically named.
    See http://pypi.python.org/pypi/zc.recipe.egg

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s