path: root/doc/forum/running_propellor_as_a_library.mdwn
diff options
authorarnaud.oqube@c9b8c7ea33f1dea0b7a5485b86825c5bfa9efbf72015-05-27 13:31:03 +0000
committeradmin2015-05-27 13:31:03 +0000
commit716ce552b1ca173affe047266b84d944d7b62e51 (patch)
tree32436b03e1632599e30a4cc4f3d68a98d26af921 /doc/forum/running_propellor_as_a_library.mdwn
parent53f2646c4520e5c788d4b60dae63049222737acc (diff)
Diffstat (limited to 'doc/forum/running_propellor_as_a_library.mdwn')
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/forum/running_propellor_as_a_library.mdwn b/doc/forum/running_propellor_as_a_library.mdwn
new file mode 100644
index 00000000..a6945308
--- /dev/null
+++ b/doc/forum/running_propellor_as_a_library.mdwn
@@ -0,0 +1,4 @@
+I would like to define my propellor configuration using propellor as a library dependency, which removes the need to fork source repo, merge...
+I encounter an issue when trying to use propellor in that way: Everything under `Utility/` is not exported by the propellor, so cannot be used from my own properties. This is annoying because there are interesting things to build properties, like running processes...
+Would you consider exposing those modules, maybe through some other module like `Propellor.Utility` ?