|author||Joey Hess||2015-09-25 09:42:13 -0400|
|committer||Joey Hess||2015-09-25 09:42:13 -0400|
Diffstat (limited to 'doc/forum/Experimental_propellor_augeas_intergration_+_workflow_concenrs')
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/forum/Experimental_propellor_augeas_intergration_+_workflow_concenrs/comment_3_a1f7f5da5f01df715173294e83af0e10._comment b/doc/forum/Experimental_propellor_augeas_intergration_+_workflow_concenrs/comment_3_a1f7f5da5f01df715173294e83af0e10._comment
new file mode 100644
@@ -0,0 +1,18 @@
+ subject="""comment 3"""
+I'm generally happy to accept new modules into propellor. However, this one
+is problimatic since it adds several new dependencies. I want to keep
+propellor's dependencies minimal.
+It could be integrated behind a flag in propellor.cabal, but then I'd need
+to worry about testing it (or not testing it) for integration when there
+So, maybe this works better as an addon module? A propellor user could then
+add it to their config.hs. Only problem I see is, it currently depends on
+propellor, so a user can't modify their propellor.cabal to depend on it.
+So you'd have to use propellor as a library.