Rudder

Currently, many actions in our packages post install scripts are redirected to /dev/null, to avoid spewing useless messages on the user's screen. This is nice, but...

This makes it very hard to analyze a problem. Usually, commands that fail are good enough to say why (or at least try) on the stdout or stderr, but we throw this information away.

I would like to implement a mechanism whereby each package's post-install script outputs any such information to /var/log/rudder/install/<package name>.log