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
8
Merge Requests
8
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
slapos.buildout
Commits
354f6536
Commit
354f6536
authored
Nov 17, 2012
by
Jim Fulton
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
removed some dangling footnote refs
parent
73b3b3b2
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
src/zc/buildout/buildout.txt
src/zc/buildout/buildout.txt
+2
-2
No files found.
src/zc/buildout/buildout.txt
View file @
354f6536
...
...
@@ -143,7 +143,7 @@ and then we'll create a source file for our mkdir recipe:
... pass
... """)
Currently, recipes must define 3 methods
[#future_recipe_methods]_
:
Currently, recipes must define 3 methods:
- a constructor,
...
...
@@ -207,7 +207,7 @@ information by adding any new files returned by the update method.
We need to provide packaging information so that our recipe can be
installed as a develop egg. The minimum information we need to specify
[#packaging_info]_
is a name. For recipes, we also need to define the
is a name. For recipes, we also need to define the
names of the recipe classes as entry points. Packaging information is
provided via a setup.py script:
...
...
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