- 06 Mar, 2007 4 commits
-
-
Jim Fulton authored
-
Jim Fulton authored
be specified in a versions section. Changed the log format for picked versions.
-
Jim Fulton authored
This will allow a versions feature to be added without updating all recipes initially. Later, recipes that support custom versions will be able to override the defaults by passing options.
-
Jim Fulton authored
- The easy_install module install and build functions now accept a versions argument that supplied to mapping from project name to version numbers. This can be used to fix version numbers for required distributions and their depenencies. When a version isn't fixed, using either a versions option or using a fixed version number in a requirement, then a debug log message is emitted indicating the version picked. This is useful for setting versions options. - Added a remove testing helper function that removes files or directories.
-
- 05 Mar, 2007 2 commits
-
-
Jim Fulton authored
no longer causes voluminous setuptools output. Uisng -vv and -vvv now triggers extra setuptools output. Improved a logging message.
-
Jim Fulton authored
-
- 27 Feb, 2007 1 commit
-
-
Christian Theune authored
-
- 26 Feb, 2007 1 commit
-
-
Nathan Yergler authored
-
- 08 Feb, 2007 4 commits
-
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
spurious test failures. I'm not sure this is really necessary.
-
Jim Fulton authored
-
- 07 Feb, 2007 2 commits
-
-
Jim Fulton authored
```------------ - Added a buildout newest option, to control whether the newest distributions should be sought to meet requirements. This might also provide a hint to recipes that don't deal with distributions. For example, a recipe that manages subversion checkouts might not update a checkout if newest is set to "false". - The recipe-testing support setUp function now adds the name *buildout* to the test namespace with a value that is the path to the buildout script in the sample buildout. This allows tests to use >>> print system(buildout), rather than: >>> print system(join('bin', 'buildout')), Bugs Fixed ``` ------- - Paths returned from update methods replaced lists of installed files rather than augmenting them.
-
Jim Fulton authored
Also added a missing tests for upgrading.
-
- 05 Feb, 2007 1 commit
-
-
Jim Fulton authored
allow for getting less than the newest but still getting what's necessary.
-
- 24 Jan, 2007 2 commits
-
-
Jim Fulton authored
Explicitly specifying a Python executable failed if the output of running Python with the -V option included a 2-digit (rather than a 3-digit) version number.
-
Jim Fulton authored
-
- 22 Jan, 2007 1 commit
-
-
Jim Fulton authored
Feature Changes --------------- - By popular demand, added a -o command-line option that is a short hand for the assignment buildout:offline=true. Bugs Fixed ---------- - When deciding whether recipe develop eggs had changed, buildout incorrectly considered files in .svn and CVS directories.
-
- 17 Jan, 2007 4 commits
-
-
Jim Fulton authored
-
Jim Fulton authored
Added initialization and arguments options to the scripts recipe.
-
Jim Fulton authored
-
Jim Fulton authored
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.
-
- 16 Jan, 2007 1 commit
-
-
Jim Fulton authored
These are used and tested indirectly in various ways.
-
- 07 Jan, 2007 1 commit
-
-
Christian Theune authored
-
- 07 Dec, 2006 8 commits
-
-
Jim Fulton authored
-
Jim Fulton authored
---------- - https://bugs.launchpad.net/products/zc.buildout/+bug/71246 Buildout extensions installed as eggs couldn't be loaded in offline mode.
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
---------- - Uninstall recipes weren't loaded correctly in cases where no parts in the (new) configuration used the recipe egg.
-
Jim Fulton authored
--------------- - A new command-line argument, -U, suppresses reading user defaults. - You can now suppress use of an installed-part database (e.g. .installed.cfg) by sprifying an empty value for the buildout installed option.
-
Jim Fulton authored
depended on were installed too. This is nice under normal circumstances, but when the install command is used with a list of parts, then the promise is that *only* those parts will be installed. This is an important use case, because it can speed development.
-
- 05 Dec, 2006 8 commits
-
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
Use the logical size instead.
-
Amos Latteier authored
Both now must use the same name. Thus there is no need for a part 'uninstall' option.
-
Amos Latteier authored
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
on windows.
-