This was split off from #606 as a possible enhancement for libtaskotron.

There has been an idea of creating a new taskotron profile (the current ones are development and production, something like taskotron_development). If this profile was active, we would have some strong assumptions that would make possible to automate certain tasks. For example, we would assume we run from a git checkout. In that case we should be theoretically able to automatically build a new RPM and install it onto the client. Building RPMs is slow, but it's better than the current state. We could also try to copy the current git checkout instead of building RPMs, and install it on the client. That would be fast, and it wouldn't even require you to commit your changes. Since we will have access to specfile and requirements.py, we could even install any recently-added deps, update packages to match development versions, etc. We can basically set up exactly the same environment as the developer has. This approach seems promising, but it isn't well thought out yet and it includes creation of another taskotron profile, adding to confusion of people studying the documentation and the config file.