summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--doc/forum/Systemd.container_produces_non-standard_systemd_container/comment_8_f0968beaac7e73e192c0d59fe0637c0e._comment7
-rw-r--r--doc/todo/use_stack_for_remote_building_propellor.mdwn3
-rw-r--r--doc/todo/use_stack_for_remote_building_propellor/comment_1_8a97e9ce919fa59f2e36bdd4eb3a7174._comment24
3 files changed, 34 insertions, 0 deletions
diff --git a/doc/forum/Systemd.container_produces_non-standard_systemd_container/comment_8_f0968beaac7e73e192c0d59fe0637c0e._comment b/doc/forum/Systemd.container_produces_non-standard_systemd_container/comment_8_f0968beaac7e73e192c0d59fe0637c0e._comment
new file mode 100644
index 00000000..ac192232
--- /dev/null
+++ b/doc/forum/Systemd.container_produces_non-standard_systemd_container/comment_8_f0968beaac7e73e192c0d59fe0637c0e._comment
@@ -0,0 +1,7 @@
+[[!comment format=mdwn
+ username="gueux"
+ subject="comment 8"
+ date="2016-05-24T13:19:44Z"
+ content="""
+https://github.com/systemd/systemd/issues/2914 is fixed in systemd 230
+"""]]
diff --git a/doc/todo/use_stack_for_remote_building_propellor.mdwn b/doc/todo/use_stack_for_remote_building_propellor.mdwn
new file mode 100644
index 00000000..265596df
--- /dev/null
+++ b/doc/todo/use_stack_for_remote_building_propellor.mdwn
@@ -0,0 +1,3 @@
+Among other features [stack](https://github.com/commercialhaskell/stack/) provides a clean and deep dependency management system that even takes care of installing toolchain (ghc, alex, happy, cabal...) in a segregated environment. Building remote propellor with stack would remove the limitation that code should be compilable with stock ghc from package manager. I have done some preliminary work on this feature in my [github clone](https://github.com/abailly/propellor) for propellor, currently from 2.17.2 branch (I wanted to reuse existing properties). The code is mostly in [Bootstrap](https://github.com/abailly/propellor/blob/master/src/Propellor/Bootstrap.hs) and is currently limited to linux systems. Adapting to FreeBsd should be straightforward as this is supported by slack and there are native builds available.
+
+If there is interest in such a feature I would be happy to move it to HEAD and provide a patch.
diff --git a/doc/todo/use_stack_for_remote_building_propellor/comment_1_8a97e9ce919fa59f2e36bdd4eb3a7174._comment b/doc/todo/use_stack_for_remote_building_propellor/comment_1_8a97e9ce919fa59f2e36bdd4eb3a7174._comment
new file mode 100644
index 00000000..90dfafbc
--- /dev/null
+++ b/doc/todo/use_stack_for_remote_building_propellor/comment_1_8a97e9ce919fa59f2e36bdd4eb3a7174._comment
@@ -0,0 +1,24 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2016-05-29T18:50:07Z"
+ content="""
+`stack install propellor` is already supported, and when `propellor --init`
+detects it was installed that way, it will set up the user's propellor
+config to also be built using stack locally (via `git config
+propellor.buildsystem stack`).
+
+Supporting using stack to build propellor on the Host too is
+the missing part, and something I'd take a patch for.
+
+Your patch as it stands discards the cabal support.
+But, I personally want to continue building propellor with cabal on my
+Hosts, at least until stack is available in Debian stable, and
+probably longer. (I use Debian's ghc and haskell packages for other things
+on my hosts, so using stack would waste disk space.)
+
+I feel there needs to be a way to configure this. It would probably be fine to
+use stack on the remote host if the local propellor repository has
+`git config propellor.buildsystem stack` set. Or perhaps it should be
+configured in the config.hs.
+"""]]