Some requirements: - stabilize core bunsen.py interface (get rid of TODOs) - decide how to identify the current repo to run analysis scripts against (should work similarly to Git) + workflow to override/update analysis scripts - implement Python packaging + dependency info - follow https://docs.fedoraproject.org/en-US/packaging-guidelines/Python to make spec file
This is still a relevant PR for the new master branch. (Especially since the new code includes a configure/make sequence and requires environment variables to be set, hence 'installing' Bunsen is no longer just a matter of cloning the Git repo and creating .bunsen/config.)