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
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Boxiang Sun
slapos.buildout
Commits
4215b4b7
Commit
4215b4b7
authored
18 years ago
by
Jim Fulton
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Removed bogus issue.
parent
86740374
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
0 additions
and
18 deletions
+0
-18
todo.txt
todo.txt
+0
-18
No files found.
todo.txt
View file @
4215b4b7
...
...
@@ -37,21 +37,3 @@
- Local download cache
- Logging
Issue:
- If recipes require zc.buildout, there are weird problems for the
tests, because we'll try to get zc.buildout when the test runs the
recipe and there might not be a convenient way for it to do that.
This is really a case of "plugins". A plugin system has to be
prepared to dynamically find eggs of the thing doing the plugging.
This is a potential problem for my plan of just including eggs (or
link dests) in generated script paths, as that would prevent a
plugin system from finding the eggs already loaded. We really need
to include the egg dirs as well. This feels a bit weird.
Suppose you have some package, X and X supports plugins. If X loads
a plugin and the plugin requires X, then we need to be able to find
X's egg. Furthermore, if we upgrade the plugin when we find it, we
will end up upgrading X, which makes no sense.
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