propellor/src/wrapper.hs, branch master gnusosa's centralized propellor repository for hosts spin-up. https://git.gnusosa.net/propellor/atom?h=master 2018-04-22T16:19:40Z separate Hs-Source-Dirs for binaries 2018-04-22T16:19:40Z Joey Hess joeyh@joeyh.name 2018-04-22T16:15:35Z urn:sha1:d8d2faece72eabd18c2ff303e5fb63c3a69961f6 This is a trick I only just learned about, see https://stackoverflow.com/questions/6711151/how-to-avoid-recompiling-in-this-cabal-file#6711739 Significantly increased propellor build speed when your config.hs is in a fork of the propellor repository, by avoiding redundant builds of propellor library. Also avoids needing to list all the build deps 3 times. Also avoids cabal 2.x wanting every module to be listed 3 times. Note that the bulk of wrapper.hs had to move into the propellor library, since that code depended on stuff not exposed by the library. This commit was sponsored by Henrik Riomar on Patreon. GHC's fileSystemEncoding is used for all String IO, to avoid encoding-related crashes in eg, Propellor.Property.File. 2016-12-24T19:14:05Z Joey Hess joeyh@joeyh.name 2016-12-24T19:14:05Z urn:sha1:44bf67b7a2da75ef80e32d6409cc41a6ab8b6ffe check that config.hs mentions "Propellor" 2016-11-12T05:41:30Z Joey Hess joeyh@joeyh.name 2016-11-12T05:41:30Z urn:sha1:bde6a58ef862ab01ee89a07d815fad4a51361b5b from eg, "import Propellor" The propellor wrapper checks if ./config.hs exists; if so it runs using the configuration in the current directory, rather than ~/.propellor/config.hs 2016-11-12T05:34:19Z Joey Hess joeyh@joeyh.name 2016-11-12T05:34:19Z urn:sha1:b4adaf75a36d6d6425df820c46023a32e79bb6df The config,hs name now seems a bit badly chosen, propellor.hs would be less ambiguous. To avoid accidentially running with a config.hs for something else, the file content has to contain "Propellor". Note that checkRepoUpToDate is only run for ~/.propellor/. I guess propellor configs in other directories won't have been set up that way, and it would take some changes to make that not hardcode use of dotPropellor. There's a new security boundary here, since running propellor looks at the cwd, whose contents might not be user the user's control. The security checks I added for this seem pretty good, but even if they can be bypassed, this is not much different than `make` using the Makefile in cwd. This commit was sponsored by Ole-Morten Duesund on Patreon. Fix build with directory-1.2.6.2. 2016-04-28T19:31:35Z Joey Hess joeyh@joeyh.name 2016-04-28T19:31:35Z urn:sha1:2e513dc98c51eca1cdfce3715b4a017be39734f7 It's now exporting a conflicting isSymbolicLink https://github.com/haskell/directory/issues/52 Only a few places in propellor use isSymbolicLink, but to prevent future problems, made as much of it as possible import Utility.Directory, which re-exports System.Directory without the conflicting symbol. (Utility.Tmp and System.Console.Concurrent.Internal cannot import Utility.Directory due to cycles, and don't use isSymbolicLink anyway.) make sure that the wrapper runs propellor in the foreground 2016-04-02T05:59:38Z Joey Hess joeyh@joeyh.name 2016-04-02T05:59:38Z urn:sha1:db2d46246c5772c12aa8cf64ea604b65d164a7b0 typo 2016-04-02T05:52:09Z Joey Hess joeyh@joeyh.name 2016-04-02T05:51:01Z urn:sha1:828830eace62dba7d75b656142d83f8396fd2968 avoid wrapper building propellor unnessessarily 2016-04-02T05:49:01Z Joey Hess joeyh@joeyh.name 2016-04-02T05:49:01Z urn:sha1:1c70d2e18917973723bf836fdc1f789532d96811 separate propellor --init 2016-04-02T01:20:13Z Joey Hess joeyh@joeyh.name 2016-04-02T01:20:13Z urn:sha1:1dc914a71c94e0395641565e5891a2dc33ba1b35 setup gpg key in initial setup process 2016-04-01T23:48:23Z Joey Hess joeyh@joeyh.name 2016-04-01T23:34:27Z urn:sha1:93b083f3a1204a7cf4452b5ebd589dd77d25dbac