Some necessary decisions around OS packages

[soenkeliebau]

There are a few decisions around the OS packages and how we want to build these that we need to take, which I'd like to put up for discussion here.

The current nightly packages take a very simple approach, which works for now as long as we stand up fresh test environments and pull them down after testing, but may not stand up to actual production use.

• We currently roll out a config file, but potentially the user will want to change this and we shouldn't override those changes on update. Do we simply rely on the package manager features which would create a second file for the user to merge? I'd rather provide some form of .d directory in which the user can create their settings which would override any defaults in the config file or something similar.
• Currently the systemd units are neither enabled nor started upon installation to give the option of having this as a separate, explicit step. Everybody on board with this?
• We need to add cleanup actions for uninstallation, like stopping and disabling the service and removing directories (rudimentary steps in place for rpms)
• Currently no special steps are defined for an update, any necessarry?
• aob?

[soenkeliebau]

closed in favor of stackabletech/issues#23