From 066291f50a3f8b3e10287a9e708166947a8c211c Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 28 Mar 2016 12:09:45 -0400 Subject: comment --- .../comment_7_dd93ac4f42dab131aa75fece53e51067._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/todo/detect_and_use___96__GHC__95__PACKAGE__95__PATH__96__/comment_7_dd93ac4f42dab131aa75fece53e51067._comment (limited to 'doc/todo/detect_and_use___96__GHC__95__PACKAGE__95__PATH__96__') 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. +"""]] -- cgit v1.2.3