Merge branch 'master' into typed-os-requirements

2 files changed, 21 insertions, 0 deletions

diff --git a/doc/todo/commandline_to_setup_minimal_repo.mdwn b/doc/todo/commandline_to_setup_minimal_repo.mdwn
new file mode 100644
index 00000000..5e82ed0f
--- /dev/null
+++ b/doc/todo/commandline_to_setup_minimal_repo.mdwn
@@ -0,0 +1,5 @@
+Make propellor --init be a way to set up ~/.propellor. This would allow
+parameters, like --minimal to clone the minimal config repo instead of the
+full one, or --stack to set up ~/.propellor to use stack.  --[[Joey]]
+
+> Or, it could be an interactive setup process. --[[Joey]]
diff --git a/doc/todo/detect_and_use___96__GHC__95__PACKAGE__95__PATH__96__/comment_7_dd93ac4f42dab131aa75fece53e51067._comment b/doc/todo/detect_and_use___96__GHC__95__PACKAGE__95__PATH__96__/comment_7_dd93ac4f42dab131aa75fece53e51067._comment
new file mode 100644
index 00000000..5a488d25
--- /dev/null
+++ b/doc/todo/detect_and_use___96__GHC__95__PACKAGE__95__PATH__96__/comment_7_dd93ac4f42dab131aa75fece53e51067._comment
@@ -0,0 +1,16 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 7"""
+ date="2016-03-28T16:06:43Z"
+ content="""
+sm noticed that running the propellor wrapper after stack install propellor
+sets up ~/.propellor/ but fails to build in there, because it uses cabal.
+
+So, it appeared to him as if the propellor command didn't accept switches,
+since it never got to the point of running propellor-config. Which is
+pretty confusing behavior.
+
+To fully support stack, the wrapper or build process would need to notice
+that it was installed using stack, and build using stack. This conflicts
+somewhat with my idea about noticing if stack.yaml exists as the flag.
+"""]]