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
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Kirill Smelkov
slapos.buildout
Commits
d05717a2
Commit
d05717a2
authored
Sep 05, 2016
by
Reinout van Rees
Committed by
GitHub
Sep 05, 2016
Browse files
Options
Browse Files
Download
Plain Diff
Merge pull request #275 from jean/master
Editing while reading
parents
0e4f731c
93d1d037
Changes
2
Expand all
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
352 additions
and
336 deletions
+352
-336
src/zc/buildout/bootstrap.txt
src/zc/buildout/bootstrap.txt
+15
-15
src/zc/buildout/buildout.txt
src/zc/buildout/buildout.txt
+337
-321
No files found.
src/zc/buildout/bootstrap.txt
View file @
d05717a2
...
...
@@ -47,7 +47,7 @@ Make sure the bootstrap script actually works::
X...
d zc.buildout-...egg
By default it gets the latest version:
By default it gets the latest version:
:
>>> buildout_script = join(sample_buildout, 'bin', 'buildout')
>>> if sys.platform.startswith('win'):
...
...
@@ -59,8 +59,8 @@ By default it gets the latest version:
'/sample/eggs/zc.buildout-22.0.0...egg',
]...
Now trying the `
--buildout-version` option, that let you define a version for
`zc.buildout
`.
Now trying the `
`--buildout-version`` option, that let you define a version
for ``zc.buildout`
`.
Let's try with an unknown version::
...
...
@@ -73,7 +73,7 @@ Let's try with an unknown version::
No local packages or...download links found for zc.buildout==UNKNOWN
...
Now let's try with `
2.0.0
`, which happens to exist::
Now let's try with `
`2.0.0`
`, which happens to exist::
>>> print_('X'); print_(system(
... zc.buildout.easy_install._safe_arg(sys.executable)+' '+
...
...
@@ -81,7 +81,7 @@ Now let's try with `2.0.0`, which happens to exist::
... # doctest: +ELLIPSIS
X...Generated script '/sample/bin/buildout'...X
Let's make sure the generated `
buildout
` script uses it::
Let's make sure the generated `
`buildout`
` script uses it::
>>> print_(open(buildout_script).read()) # doctest: +ELLIPSIS
#...
...
...
@@ -90,10 +90,10 @@ Let's make sure the generated `buildout` script uses it::
'/sample/eggs/zc.buildout-2.0.0...egg',
]...
Now trying the `
--setuptools-version` option, that let you define a version for
`setuptools
`.
Now trying the `
`--setuptools-version`` option, that lets you define a version
for ``setuptools`
`.
Now let's try with `
8.0
`, which happens to exist::
Now let's try with `
`8.0`
`, which happens to exist::
>>> print_('X'); print_(system(
... zc.buildout.easy_install._safe_arg(sys.executable)+' '+
...
...
@@ -101,7 +101,7 @@ Now let's try with `8.0`, which happens to exist::
... # doctest: +ELLIPSIS
X...Generated script '/sample/bin/buildout'...X
Let's make sure the generated `
buildout
` script uses it::
Let's make sure the generated `
`buildout`
` script uses it::
>>> print_(open(buildout_script).read()) # doctest: +ELLIPSIS
#...
...
...
@@ -110,7 +110,7 @@ Let's make sure the generated `buildout` script uses it::
'/sample/eggs/zc.buildout-...egg',
]...
Now let's try specifying both `
zc.buildout` and `setuptools
` to versions
Now let's try specifying both `
`zc.buildout`` and ``setuptools`
` to versions
which happens to exist::
>>> print_('X'); print_(system(
...
...
@@ -119,7 +119,7 @@ which happens to exist::
... # doctest: +ELLIPSIS
X...Generated script '/sample/bin/buildout'...X
Let's make sure the generated `
buildout
` script uses it::
Let's make sure the generated `
`buildout`
` script uses it::
>>> print_(open(buildout_script).read()) # doctest: +ELLIPSIS
#...
...
...
@@ -128,8 +128,8 @@ Let's make sure the generated `buildout` script uses it::
'/sample/eggs/zc.buildout-2.0.0...egg',
]...
For a completely offline install we want to avoid downloading
ez_setup.py
,
specify the setuptools version, and to reuse the setuptools zipfile
.
For a completely offline install we want to avoid downloading
``ez_setup.py``
,
specify the setuptools version, and to reuse the setuptools zipfile
::
>>> try:
... from urllib.request import urlopen
...
...
@@ -160,12 +160,12 @@ specify the setuptools version, and to reuse the setuptools zipfile.
'/sample/eggs/zc.buildout-2.0.0...egg',
]...
You can ask
bootstrap.py
for its version. This is really the day the last
You can ask
``bootstrap.py``
for its version. This is really the day the last
change was made. A date leads to less confusion than a version number separate
from buildout's own version number. Similarly, tracking buildout's version
number leads to bootstraps with a new version number but without changes or to
bootstraps with version number from an already-older buildout. So: a date is
best
.
best
::
>>> print_('X'); print_(system(
... zc.buildout.easy_install._safe_arg(sys.executable)+' '+
...
...
src/zc/buildout/buildout.txt
View file @
d05717a2
This diff is collapsed.
Click to expand it.
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