Commit ecf7c4f2 authored by Chris Withers's avatar Chris Withers

Try and make this section make sense.

I hope I haven't changed any intended meaning.
parent 893e343b
...@@ -94,11 +94,9 @@ Our buildout script has been updated to use the new eggs: ...@@ -94,11 +94,9 @@ Our buildout script has been updated to use the new eggs:
if __name__ == '__main__': if __name__ == '__main__':
zc.buildout.buildout.main() zc.buildout.buildout.main()
There are a number of cases in which the updates don't happen. Now, let's recreate the sample buildout. If we specify constraints on
Let's recreate the sample buildout. One case is the one in which we the versions of zc.buildout and setuptools to use, running the
specify versions of zc.buildout and setuptools for which the don't buildout will install earlier versions of these packages:
match. If we update out configuration file to specify an older
version:
>>> write(sample_buildout, 'buildout.cfg', >>> write(sample_buildout, 'buildout.cfg',
... """ ... """
...@@ -114,7 +112,7 @@ version: ...@@ -114,7 +112,7 @@ version:
... recipe = showversions ... recipe = showversions
... """ % dict(new_releases=new_releases)) ... """ % dict(new_releases=new_releases))
We'll actually "upgrade" to an earlier version. Now we can see that We actually "upgrade" to an earlier version.
>>> print system(buildout), >>> print system(buildout),
Upgraded: Upgraded:
...@@ -127,6 +125,9 @@ We'll actually "upgrade" to an earlier version. ...@@ -127,6 +125,9 @@ We'll actually "upgrade" to an earlier version.
zc.buildout 1.0.0 zc.buildout 1.0.0
setuptools 0.6 setuptools 0.6
There are a number of cases, described below, in which the updates
don't happen.
We won't upgrade in offline mode: We won't upgrade in offline mode:
>>> write(sample_buildout, 'buildout.cfg', >>> write(sample_buildout, 'buildout.cfg',
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment