Document how to use the Supervisor to run a non-Habitat package

[tashimi]

This is sometimes required for people who want to manage and deploy and package proprietary vendored software that they don’t own, so they don’t break their support license agreement.

One example we've done in the past used a tarball of a COTS product already compiled to link against Red Hat provided libraries. The Habitat plan retrieved that tarball, expanded it to $pkg_prefix during build, and provided config templates and init/run/health hooks for runtime supervision. The run command was pretty much what the COTS product expected. It would fail to run if the host running the Hab service did not already have the RHEL packages for the libraries it needed.

We should add a knowledge doc about this in our docs page so people have some hints on how to get started when they need to do this.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.