comment

1 files changed, 17 insertions, 0 deletions

diff --git a/doc/todo/use_stack_for_remote_building_propellor/comment_5_10e2bf7ca762b53632dd4fb86f1ce0ae._comment b/doc/todo/use_stack_for_remote_building_propellor/comment_5_10e2bf7ca762b53632dd4fb86f1ce0ae._comment
new file mode 100644
index 00000000..c39282c0
--- /dev/null
+++ b/doc/todo/use_stack_for_remote_building_propellor/comment_5_10e2bf7ca762b53632dd4fb86f1ce0ae._comment
@@ -0,0 +1,17 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 5"""
+ date="2016-05-31T16:25:09Z"
+ content="""
+Following spwhitton's idea, this would involve adding a new property which 
+configures the host it's attached to to build propellor using stack.
+
+This can be accomplished by having the property set some Info which can
+be looked at when propellor is deploying itself to the host, 
+as shown in the precompiled branch.
+
+I guess most people who want to build
+propellor with stack would want to do that on all hosts. You could have a
+`[Host] -> [Host]` function that added the stack property to a list of
+hosts I suppose.
+"""]]