gnusosa's centralized propellor repository for hosts spin-up. https://git.gnusosa.net/propellor/atom?h=master 2018-04-23T19:20:25Z 2018-04-23T19:20:25Z Joey Hess joeyh@joeyh.name 2018-04-23T19:20:25Z urn:sha1:f2bb9a3db7ccb5fc0e64920017d305715b34ba95 Tested build with ghc 8.4 now. 2017-03-19T19:44:49Z Joey Hess joeyh@joeyh.name 2017-03-19T19:44:49Z urn:sha1:7d3537e2b5462880242bf3f7c4f7aa75f2727d15 2017-03-19T00:16:40Z Joey Hess joeyh@joeyh.name 2017-03-19T00:16:40Z urn:sha1:b402430cf24ae71c178731a0241f89cc7d1b3e98 2017-03-15T18:09:07Z Joey Hess joeyh@joeyh.name 2017-03-15T18:09:07Z urn:sha1:52ca81661f156122a3a5d4a438fea83e067215ac * Property types changed to use a Maybe (Propellor Result). (API change) * When Nothing needs to be done to ensure a property, propellor will avoid displaying its description at all. The doNothing property is an example of such a property. This is mostly in preparation for Monoid instances for Property types, but is's also nice that anything that uses doNothing will avoid printing out any message at all. At least, I think it probably is. It might potentially be confusing for something that sometimes takes an action and sometimes resolves to doNothing and in either case has a description set to not always show the description. If this did turn out to be confusing, the change to doNothing could be reverted. This commit was sponsored by Boyd Stephen Smith Jr. on Patreon. 2016-03-27T23:59:20Z Joey Hess joeyh@joeyh.name 2016-03-27T23:59:20Z urn:sha1:9d6dc29555b8499d8ae6c73c891b0b5dc19f83e5 2016-03-26T23:31:23Z Joey Hess joeyh@joeyh.name 2016-03-26T23:31:23Z urn:sha1:36e97137e538de401bd0340b469e10dca5f4b475 Renamed several utility functions along the way. 2016-03-25T22:39:50Z Joey Hess joeyh@joeyh.name 2016-03-25T22:39:50Z urn:sha1:ce8d34d094be30e1432ecaaae81b188671180624 Ssh is WIP and failing to compile quite badly 2016-03-25T20:20:32Z Joey Hess joeyh@joeyh.name 2016-03-25T20:20:32Z urn:sha1:f01776d64b1b8fcf89903d0de1ffe27f10d620ee and note that it's not meant to be used by regular users 2016-03-25T18:24:09Z Joey Hess joeyh@joeyh.name 2016-03-25T18:24:09Z urn:sha1:9768434f5fa2f2ed0bbb0212763a76471186a3cd 2016-03-25T18:04:40Z Joey Hess joeyh@joeyh.name 2016-03-25T18:04:40Z urn:sha1:91d1833155a2e8be2c435d0a92a750cc9d2f30b5 I wanted to keep propertyList [foo, bar] working, but had some difficulty making the type class approach work. Anyway, that's unlikely to be useful, since foo and bar probably have different types, or could easiy have their types updated breaking it.