Introduction

Formerly collective.recipe.bootstrap

buildout.bootstrap is a Buildout extension that adds a Buildout bootstrap.py file to your buildout.

It satisfies the use case:

"I want to keep my buildout's bootstrap.py file up to date without having to download it manually."

It also makes it easy to add a bootstrap.py file to a buildout created via buildout init e.g.:

$ buildout init

After running this command, you have a buildout.cfg that looks like this:

[buildout]
parts =

And you can now add the extension like so:

[buildout]
extensions = buildout.bootstrap
parts =

Run buildout again and afterward you should have a bootstrap.py file. Once you have a bootstrap.py file you can bootstrap the buildout via:

$ python bootstrap.py -d (-d to specify distribute)

If you still don't understand, consider the following: with this extension you can avoid having to type:

$ curl -O https://raw.github.com/buildout/buildout/1/bootstrap/bootstrap.py

You typically use this extension when you have created a new buildout and want to:

Installation

Add buildout.bootstrap to the extensions parameter in the buildout section of your buildout.cfg e.g.:

[buildout]
extensions = buildout.bootstrap
parts =

Changes

1.4.4 (2013-01-12)

  • Update buildout/bootstrap/__init__.py [do3cc]
  • Working error codes [do3cc]

1.4.3 (2012-11-01)

  • Don't bother updating bootstrap.py when the buildout is running in offline (-o) mode [nutjob]

1.4.2 (2012-08-18)

1.4.1 (2012-05-16)

1.4.0 (2012-05-16)

  • Support Python 2.4 [aclark]
  • Doc fix [davidjb]

1.3.0 (2012-04-06)

  • Clean up package. Buildout moved to github. Remove option to specify version (based on svn tag) [aclark]

1.2 (2010-08-13)

  • Add option to specify version (based on svn tag) [aclark]
  • Add test stubs [aclark]

1.1 (2010-08-13)

  • Rename and repackage as Buildout extension [aclark]

1.0 (2009-12-19)

  • Clean up docs [aclark]

0.1 (2009-08-07)

  • Add initial functionality [aclark]
  • Created recipe with ZopeSkel [aclark]

Contributors