OH 2.5.12 docker outpost for legacy 1.x bindings

As far as I’m aware, the bundle will activate as soon as you install a binding that depends upon it. The add-ons define what they depend upon so should activate stuff on their own, but only when properly installed through the API. If you just drop the jar file into the addons folder you’ll have to activate the add-on’s dependencies on your own.

I remember this was a problem with the Zwave binding which depends on the serial device bundle.