• Add command completions for zsh (and bash?)
• Completions for:
  • module names (using modman list)
  • cmd flags

• Allow optional configuration dependent on system metadata, such as:

  • hostname
  • host type (server, graphical system etc.)

• Configuration of meta-hosts which are collections of hosts that can be referred to as a group

Current Behaviour

N/A

Expected Behaviour

• Specify Arch Linux package dependencies (AUR using yay?)
  • User can install dependencies explicitly or as dependencies (in the pacman sense).
  • Optional dependencies for additional functionality (e.g. addditional aliases for shell etc.)

Current Behaviour

Although a package is verified at runtime, a partial install/uninstall may result from modifications between verifying a package and installing it. This is an unbounded delay due to the possibility of arbitrary init/cleanup scripts. In fact, the scripts themselves may cause a future package to be uninstallable.

Required behaviour

Implement a simple transaction system which requires:

• All files to be modified successfully
• Any script to run successfully

This can be implemented pretty simply by keeping track of progress and reverting if something wrong. This will not guarantee full atomicity (can have a failure cleaning up; fs changes between operations), but this should be good enough.

Additional complexity results from the separation of init and cleanup scripts. Although reverting files is easy, reverting the result of running an arbitrary script is not. A potential solution is to always require neither or both and pass the complexity of cleaning up to the scripts. Will also possibly require additional state to be generated about the install status of a module (in order to revert a failed uninstall without guessing whether the package was installed in the first place).