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
4d5f3f33
Commit
4d5f3f33
authored
Aug 25, 2012
by
Hanno Schlichting
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Clarify Makefile instructions, remove me from explicit travis sender list
parent
c908ce04
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
9 additions
and
7 deletions
+9
-7
.travis.yml
.travis.yml
+0
-1
DEVELOPERS.txt
DEVELOPERS.txt
+9
-6
No files found.
.travis.yml
View file @
4d5f3f33
...
@@ -10,7 +10,6 @@ branches:
...
@@ -10,7 +10,6 @@ branches:
notifications
:
notifications
:
email
:
email
:
-
hanno@hannosch.eu
-
buildout-development@googlegroups.com
-
buildout-development@googlegroups.com
install
:
install
:
...
...
DEVELOPERS.txt
View file @
4d5f3f33
...
@@ -11,14 +11,17 @@ When you're developing buildout itself, you need to know two things:
...
@@ -11,14 +11,17 @@ When you're developing buildout itself, you need to know two things:
dev.py``.
dev.py``.
For your convenience we provide a Makefile to build various Python versions
For your convenience we provide a Makefile to build various Python versions
in subdirectories of the buildout checkout. To use this do::
in subdirectories of the buildout checkout. To use these and run the tests
with them do::
make PYTHON_VER=2.6 build
make PYTHON_VER=2.6 build
make PYTHON_VER=2.7 build
make PYTHON_VER=3.2 build
In order to run the tests, you can then use::
make PYTHON_VER=2.6 test
make PYTHON_VER=2.6 test
make PYTHON_VER=2.7 build
make PYTHON_VER=2.7 test
make PYTHON_VER=2.7 test
make PYTHON_VER=3.2 build
make PYTHON_VER=3.2 test
make PYTHON_VER=3.2 test
The actual Python compilation is only done once and then re-used. So on
subsequent builds, only the development buildout itself needs to be redone.
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