Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
S
slapos.buildout
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Boxiang Sun
slapos.buildout
Commits
37bce56b
Commit
37bce56b
authored
Feb 10, 2013
by
Jim Fulton
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Consolidate version 2 changes and add some important omissions.
parent
396f021e
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
80 additions
and
93 deletions
+80
-93
CHANGES.rst
CHANGES.rst
+80
-93
No files found.
CHANGES.rst
View file @
37bce56b
Change History
**************
2.0.0b2 (2013-02-02)
====================
- Integrated the `buildout-versions
<http://packages.python.org/buildout-versions/>`_ extension into buildout
itself. For this, a few options were added to buildout:
- If ``show-picked-versions`` is set to true, all picked versions are
printed at the end of the buildout run. This saves you from running
buildout in verbose mode and extracting the picked versions from the
output.
- If ``update-versions-file`` is set to a filename (relative to the buildout
directory), the ``show-picked-versions`` output is appended to that file.
2.0.0b1 (2013-01-21)
====================
- Buildout options can be given on the command line using the form::
option_name=value
as a short-hand for::
buildout:option_name=value
- The ``versions`` option now defaults to ``versions``, so you no
longer need to include::
versions = versions
in a ``buildout`` section when pinning versions.
A ``versions`` section is added, if necessary, if a ``versions``
option isn't used.
- Buildout-defined default versions are included in the versions
section, if there is one.
- The ``buildout:zc.buildout-version`` and
``buildout:distribute-version`` options have been removed in favor
of providing version constraints in a versions section.
- Error if install-from-cache and offline are used together, because
offline largely means "don't install".
- Provide better error messages when distributions can't be installed
because buildout is run in offline mode.
Fixed: relative-paths weren't honored when bootstrapping or upgrading
(which is how the buildout script gets generated).
Fixed: initialization code wasn't included in interpeter scripts.
2.0.0 (2013-02-10)
==================
Fixed: macro inheritance bug, https://github.com/buildout/buildout/pull/37
This is a backward incompatible release of buildout that attempts to
correct mistakes made in buildout 1.
Fixed: spaces in version constriants (e.g. ``< 2``) weren't handled
correctly.
- Buildout no-longer tries to provide full or partial isolation from
system Python installations. If you want isolation, use buildout
with virtualenv, or use a clean build of Python to begin with.
2.0.0a7 (2013-01-12)
====================
Providing isolation was a noble goal, but it's implementation
complicated buildouts implementation too much.
Fixed: Blank lines in buildout configuration file sections before
options were treated as errors.
- Buildout no-longer support usiong multiple versions of Python in a
single buildout. This too was a noble goal, but added too much
complexity to the implementation.
2.0.0a6 (2013-01-11)
====================
- Changed the configuratiion file format:
Changed the configuratiion file format:
- Relative indentation in option values is retained if the first
- Relative indentation in option values is retained if the first
line is blank. (IOW, if the non-blank text is on the continuation
lines.) As in::
...
...
@@ -83,7 +31,7 @@ Changed the configuratiion file format:
In such cases, internal blank lines are also retained.
- The configuration syntax is more tightly defined, allowing fewer
- The configuration syntax is more tightly defined, allowing fewer
syntax definitions.
Buildout 1 configuration files were parsed with the Python
...
...
@@ -107,10 +55,7 @@ Changed the configuratiion file format:
- Semicolons could be used to start inline comments, but only if
preceeded by a whitespace character.
See `Configuration file syntax`_.
2.0.0a5 (2012-12-01)
====================
See `Configuration file syntax`_.
- Buildout now prefers final releases by default
(buildout:prefer-final now defaults to true, rather than false.)
...
...
@@ -118,21 +63,60 @@ See `Configuration file syntax`_.
However, if buildout is bootstrapped with a non-final release, it
won't downgrade itself to a final release.
-
Versions in versions sections can now be simple constraints, like
>=2.0dev in addition to being simple versions.
-
Buildout no-longer installs zipped eggs. (Distribute may still
install a zipped egg of itself during the bootstrapping process.)
Buildout 2 leverages this to make sure it uses
zc.recipe.egg>=2.0.0a3, which mainly matters for Python 3
.
- Buildout no-longer supports setuptools. It now uses distribute
exclusively
.
2.0.0a4 (2012-11-19)
====================
- Integrated the `buildout-versions
<http://packages.python.org/buildout-versions/>`_ extension into buildout
itself. For this, a few options were added to buildout:
Tweaked PyPi page.
- If ``show-picked-versions`` is set to true, all picked versions are
printed at the end of the buildout run. This saves you from running
buildout in verbose mode and extracting the picked versions from the
output.
2.0.0a3 (2012-11-19)
====================
- If ``update-versions-file`` is set to a filename (relative to the buildout
directory), the ``show-picked-versions`` output is appended to that file.
New features:
- Buildout options can be given on the command line using the form::
option_name=value
as a short-hand for::
buildout:option_name=value
- The ``versions`` option now defaults to ``versions``, so you no
longer need to include::
versions = versions
in a ``buildout`` section when pinning versions.
A ``versions`` section is added, if necessary, if a ``versions``
option isn't used.
- Buildout-defined default versions are included in the versions
section, if there is one.
- The ``buildout:zc.buildout-version`` and
``buildout:distribute-version`` options have been removed in favor
of providing version constraints in a versions section.
- Error if install-from-cache and offline are used together, because
offline largely means "don't install".
- Provide better error messages when distributions can't be installed
because buildout is run in offline mode.
- Versions in versions sections can now be simple constraints, like
>=2.0dev in addition to being simple versions.
Buildout 2 leverages this to make sure it uses
zc.recipe.egg>=2.0.0a3, which mainly matters for Python 3.
- The buildout init command now accepts distribution requirements and
paths to set up a custom interpreter part that has the distributions
...
...
@@ -146,8 +130,6 @@ New features:
- Distutils-style scripts are also installed now (for instance pyflakes' and
docutils' scripts). https://bugs.launchpad.net/zc.buildout/+bug/422724
- Switched development location to github.com/buildout.
- Avoid sorting the working set and requirements when it won't be
logged. When profiling a simple buildout with 10 parts with
identical and large working sets, this resulted in a decrease of run
...
...
@@ -165,16 +147,21 @@ New features:
- Removed any traces of the implementation of ``extended-by``. Raise a
UserError if the option is encountered instead of ignoring it, though.
Bugs fixed:
Fixed: relative-paths weren't honored when bootstrapping or upgrading
(which is how the buildout script gets generated).
Fixed: initialization code wasn't included in interpeter scripts.
Fixed: macro inheritance bug, https://github.com/buildout/buildout/pull/37
- In the download module, fixed the handling of directories that are pointed
to by file-system paths and ``file:`` URLs.
Fixed: In the download module, fixed the handling of directories that
are pointed
to by file-system paths and ``file:`` URLs.
-
if you have a configuration with an extends entry in the [buildout]
Fixed
if you have a configuration with an extends entry in the [buildout]
section which points to a non-existing URL the result is not very
user friendly. https://bugs.launchpad.net/zc.buildout/+bug/566167
-
https://bugs.launchpad.net/bugs/697913 : Buildout doesn't honor exit code
Fixed:
https://bugs.launchpad.net/bugs/697913 : Buildout doesn't honor exit code
from scripts. Fixed.
1.4.4 (2010-08-20)
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment