propellor/src/Propellor/Property/Cmd.hs, branch mastergnusosa's centralized propellor repository for hosts spin-up.
https://git.gnusosa.net/propellor/atom?h=master2018-01-17T19:13:35ZRun su with --login2018-01-17T19:13:35ZJoey Hessjoeyh@joeyh.name2018-01-17T19:13:35Zurn:sha1:b3c795dc4784e64e2756d3736ce953a1e507f509
To avoid inheriting some problematic environment variables, such as TMP,
from the caller.
The only potential breakage from this change would be if something used
setEnv before one of the affected properties. Audited propellor's source
for that, and nothing does. Anything that did would could fail in a
concurrent context anyway.
added Propellor.Property.Bootstrap (untested)2017-04-09T19:00:48ZJoey Hessjoeyh@joeyh.name2017-04-09T19:00:33Zurn:sha1:4ba09ab6844cc3fc3e94856da22190555b697193
This commit was sponsored by Jake Vosloo on Patreon.
converted to metatypes2016-03-24T20:56:55ZJoey Hessjoeyh@joeyh.name2016-03-24T20:56:55Zurn:sha1:841a98dc1a2f6147621cf1ef2295624c9d066715Clean build with ghc 7.10.2015-12-19T20:52:53ZJoey Hessjoeyh@joeyh.name2015-12-19T20:52:53Zurn:sha1:714270abfcf6433da29dc80fdcaff740ad2a0169
Import Prelude after modules that cause warnings due to AMP change
allow using `check` on a UncheckedProperty, which yields a Property2015-12-06T18:24:44ZJoey Hessjoeyh@joeyh.name2015-12-06T18:24:44Zurn:sha1:030f13f2d0501c9fb42c8f1efa0a15fa63c94d67improve docs2015-12-06T17:30:00ZJoey Hessjoeyh@joeyh.name2015-12-06T17:30:00Zurn:sha1:f404f5ed9a79449c620fde5bd669ab41fcb8d0fbUncheckedProperty for cmdProperty et al2015-12-05T21:53:16ZJoey Hessjoeyh@joeyh.name2015-12-05T21:52:43Zurn:sha1:12548bae3d8feecce6a322162d91b827289ae824
* Properties that run an arbitrary command, such as cmdProperty
and scriptProperty are converted to use UncheckedProperty, since
they cannot tell on their own if the command truely made a change or not.
(API Change)
Transition guide:
- When GHC complains about an UncheckedProperty, add:
`assume` MadeChange
- Since these properties used to always return MadeChange, that
change is always safe to make.
- Or, if you know that the command should modifiy a file, use:
`changesFile` filename
* A few properties have had their Result improved, for example
Apt.buldDep and Apt.autoRemove now check if a change was made or not.
use execProcessConcurrent everywhere2015-10-28T03:52:02ZJoey Hessjoeyh@joeyh.name2015-10-28T03:52:02Zurn:sha1:894e2f7980052f1c331ba7780100ae0ad19856cb
Found a reasonable clean way to make Utility.Process use
execProcessConcurrent, while still allowing copying updates to it from
git-annex.
concurrent version of createProcess2015-10-28T03:24:26ZJoey Hessjoeyh@joeyh.name2015-10-28T03:19:41Zurn:sha1:51b397d0415e1efe1df412842ccb76d702140f50
Have not yet wired everything up to use this, that currently uses
Utility.Process.
export createProcess with debug logging from Propellor.Property.Cmd2015-05-30T15:05:34ZJoey Hessjoeyh@joeyh.name2015-05-30T15:05:34Zurn:sha1:aa7dcad9ba8d14013f26f6e8554901d56ef4cb5c