Date:   Tue Sep 27 21:20:50 2011 +0000
Fixed https://bugs.launchpad.net/bugs/697913 : Buildout doesn't honor exit code from scripts.

Cherry-picked from svntrunk.

  Scripts generated with relative-paths eanbled couldn't be
  symbolocally linked to other locations and still work.

  could be inserted into sys.path if a relative path was used to run
  the generated script.

locations when generating scripts.

be generated for all required eggs in addition to the eggs named
specifically.

The implementation is short and simple, but testing it required
changes in a lot of places.

leading to test failures.  The change also caused buildout to fail
with Python 2.3, which lacks a set builtin.

The list of eggs in generated scripts is sorted and duplicates removed. This prevents problems in WingIDE and makes it easier for humans to look at and use the list of eggs.

  existing buildouts.  Use::

[buildout]
    prefer-final = true

to get the new policy.  The new policy will go into effect in
  buildout 2.

  both final and non-final versions satisfy a requirement, then the
  final version will be used even if it is older.  The normal way to
  override this for specific packages is to specifically require a
  non-final version, either specifically or via a lower bound.

- There is a buildout prefer-final version that can be used with a
  value of "false"::

prefer-final = false

To prefer newer versions, regardless of whether or not they are
  final, buildout-wide.

zc.buildout logger.  This reduces noise in the output.  This change
was so far reaching, I decided to go ahead and clean up lots of log
messages, adding some missing periods and adding quotes around
requirement strings and file paths.

in easy_install.py, added logging to show why distributions are added
in verbose mode and removed recusive code to show requirement chains
when errors occurred.

https://bugs.launchpad.net/zc.buildout/+bug/71353

Also added a missing tests for upgrading.

  easy_install APIs.

- Added an eggs recipe that *just* installes eggs.

- Advertized the scripts recipe for creating scripts.

Updated some tests to deal with the fact that setuptools eggs keep
oscillating between being files and directories.

API. This allowed the tests to be simplified somewhat.

This makes things go a little faster, makes errors a little easier to
handle, and allows extensions (like the sftp extension) to influence
more of the process.

Added an option to supply entry points directly. This is useful for
packages that don't declare their entry points.

No longer generate "py-" scripts implicitly.  Added a new option,
interpreter, to request such scripts and specifu their names.

Increased default buildout logging.

generated script paths.

The sample buildout is now created using the bootstrapping mechanism
and so has a normal layout.

No longer read ~/.buildout/.default.cfg, when running tests.
(We do read a ~/.buildout/.default.cfg when testing that function, but
we manipulate HOME so that we control what is read.)

brittle and failed tests with the latest setuptools.

Added support for offline mode.

Used new API for test server management

Renamed distribution option to eggs and filled out README.txt.

distributions available. This required working around issues with
easy_install's --upgrade option:

- Upgrade is not recursive. Upgrading a distro doesn't update it's
  dependencies.

- Upgrade doesn't try very hard to avoid searching.  If we require a
  specific version of a distribution, and we already have that
  distribution, there's no point in looking for a newer one.

- easy_install has kind of odd rules for deciding when to look at an
  index.   Now that we use upgrade all the time, easy_install always
  wants to look at an index.

- We get warnings when connecting to index servers, like PyPI that 
  return text/plain not found messages.

We now have much greater control over how dependencies are
managed. We've essentially taken this over from easy_install.

Because we now always talk to an index server and because we want to
control anything we do in a test, many of the tests actually run their
own web servers.

Anyway:

- Now handle upgrades correctly, I think.

- The egg recipe can now install multiple distributions.

- We have the beginnings of offline mode.

- The internal architeture is much cleaner.

- We've merged the easy_install and egglinker modules, tossing
  some superfluois apis in the egglinker module.