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
67d0d97d
Commit
67d0d97d
authored
7 years ago
by
Nils Diefenbach
Committed by
GitHub
7 years ago
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Implement Change requests
parent
e83ad61e
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
3 deletions
+3
-3
doc/getting-started.rst
doc/getting-started.rst
+3
-3
No files found.
doc/getting-started.rst
View file @
67d0d97d
...
@@ -349,7 +349,7 @@ Buildout environment
...
@@ -349,7 +349,7 @@ Buildout environment
--------------------
--------------------
A Buildout environment includes the operating system and the Python
A Buildout environment includes the operating system and the Python
installation Buildout is
executed
with. The more a buildout depends on its
installation Buildout is
run
with. The more a buildout depends on its
environment, the more variation is likely between builds.
environment, the more variation is likely between builds.
If a Python installation is shared, packages installed by one
If a Python installation is shared, packages installed by one
...
@@ -405,7 +405,7 @@ run without this option.
...
@@ -405,7 +405,7 @@ run without this option.
Pinned
versions
Pinned
versions
_______________
_______________
You
can
also
pin
required
versions
,
and
s
o
so
in
two
ways
.
You
can
specify
them
You
can
also
pin
required
versions
,
and
d
o
so
in
two
ways
.
You
can
specify
them
where
you
list
them
,
as
in
:
where
you
list
them
,
as
in
:
..
code
-
block
::
ini
..
code
-
block
::
ini
...
@@ -537,7 +537,7 @@ With ``update-versions-file``, whenever Buildout gets the newest
...
@@ -537,7 +537,7 @@ With ``update-versions-file``, whenever Buildout gets the newest
version for a requirement (subject to requirement constraints), it
version for a requirement (subject to requirement constraints), it
appends the version to the named file, along with a comment saying
appends the version to the named file, along with a comment saying
when and why the requirement is installed. If you later want to
when and why the requirement is installed. If you later want to
upgrade a dependency,
manually update
this file with the new version. Alternatively,
upgrade a dependency,
edi
this file with the new version. Alternatively,
remove the entry altogether and Buildout will add a new entry the next
remove the entry altogether and Buildout will add a new entry the next
time it runs.
time it runs.
...
...
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