propellor

History

Joey Hess 40374c10de cron.runPropellor now runs propellor, rather than using its Makefile. This is more robust. Particularly, the Makefile would try to build propellor if there were updates, but if this build failed because a bad commit was pushed, it would abort w/o pulling any new fixed commits. Anyway, it's better to move away from using the makefile when possible as it's just for bootstrapping, and also I would like to make "make" not default to running propellor as that can be confusing behavior. (I can't change that yet; needed for upgrades. Should be fine to change after several more releases, or maybe a year..)		2014-11-25 11:33:45 -04:00
..
README.Debian	ugly workaround for lack of history in repo distributed with debian package	2014-08-19 16:40:04 -04:00
changelog	cron.runPropellor now runs propellor, rather than using its Makefile. This is more robust.	2014-11-25 11:33:45 -04:00
compat	debianization and a wrapper program for /usr/bin	2014-04-03 01:55:49 -04:00
control	maintainer	2014-11-21 21:08:30 -04:00
copyright	copyright update	2014-11-21 22:27:13 -04:00
rules	fix man page installation	2014-08-19 19:06:21 -04:00

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.