Feature: Use the .deb to bootstrap the repository.

[partim]

Ideally, the Debian package we are shipping bootstraps the repository, i.e., adds both the key and the sources.list entries to the machines. Even more ideally, it somehow then manages to replace itself with a version that is part of the repository so that it then gets updated as per the original intention.

I think this can possibly be achieved through APT policy settings?

[maertsen]

This needs some experimentation. I think installing a package will set its state to 'manual' somewhere (instead of 'auto', if it is pulled in as a dependency, which would cause removal once al dependent packages are removed). What I do know is that installation candidates are determined based on pinning priority, which one can view using apt-cache policy and set in /etc/apt/preferences.d/ or somesuch. I'm not quite sure if there is a (special?) repo and/or pinning priority associated with a package that was installed through a manual dpkg -i invocation.