From 51b74d0397d5f6498f167c7820fb4966be2be7c5 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sat, 13 May 2017 13:53:18 -0400 Subject: response --- ...ment_4_9dc985b26c29b9ce21e6c75ec03f6262._comment | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 doc/forum/Using_propellor_for_continers_only/comment_4_9dc985b26c29b9ce21e6c75ec03f6262._comment (limited to 'doc/forum/Using_propellor_for_continers_only') diff --git a/doc/forum/Using_propellor_for_continers_only/comment_4_9dc985b26c29b9ce21e6c75ec03f6262._comment b/doc/forum/Using_propellor_for_continers_only/comment_4_9dc985b26c29b9ce21e6c75ec03f6262._comment new file mode 100644 index 00000000..72d7ca83 --- /dev/null +++ b/doc/forum/Using_propellor_for_continers_only/comment_4_9dc985b26c29b9ce21e6c75ec03f6262._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 4""" + date="2017-05-13T17:42:41Z" + content=""" +The way propellor handles running in a chroot or container is it exports +its binary and support files into the container. This way the +haskell code can run in a container, rather than being limited to +only running shell commands in the container, and without needing ghc in +the container. + +It does use the hardcoded `localdir` for that. +It would certianly be possible to make it use propellor in a different +location, perhaps using `getExecutablePath`. + +Since the git-annex outside the container passes command-line options to +the one running inside the container to tell it what to do, using +`mainProperties` would also not work since that does not look at +command-line options. It would need to use `defaultMain` or +`processCmdLine` and dispatch itself, or something.. +"""]] -- cgit v1.2.3