This is not a complete fix for the problem that Info doen't propigate from the called property when code does something like: do hostname <- asks hostName ensureProperty $ foo hostname Instead, I just eliminated the need to implement hasPassword that way, by making the PrivData Info use a HostContext which automatically gets the right hostname passed to it. All other uses of withPrivData don't have the problem. It's still possible for the user to run into the problem if they write something like the above, where foo is a property that uses privdata. However, all properties that take a Context now also accept a HostContext, so it's at least less likely the user needs to write that. |
||
---|---|---|
.. | ||
README.Debian | ||
changelog | ||
compat | ||
control | ||
copyright | ||
rules |
README.Debian
The Debian package of propellor ships its full source code because propellor is configured by rebuilding it, and embraces modification of any of the source code. /usr/bin/propellor is a wrapper which will set up a propellor git repository in ~/.propellor/, and run ~/.propellor/propellor if it exists. Edit ~/.propellor/config.hs to configure it. Note that upgrading the propellor package will not update your ~/.propellor/ repository. This is because you may have local changes to the source, or may need to adapt your config.hs to work with the new version of propellor. Instead, if your ~/.propellor/ is from an older version of propellor, /usr/bin/propellor will warn that it's out of date, and tell you how to merge in the changes.