Comment 9 for bug 1280337

The dependency chain here looks like this:

unity -> bamfdaemon -> libunity-webapps0 -> unity-webapps-service -> webapp-container -> webbrowser-app.

My initial feeling was that bamfdaemon just shouldn't depend on libunity-webapps0, because we dropped a bunch of webapps code from bamf following the switch to the container, however upon looking at the code there it seems bamf and libunity-webapps are tightly integrated, so that seemed like a nontrivial task to split.

Then I started looking at the chain and it wasn't clear to me whether unity-webapp-service should stop depending on webapp-container, or whether webapp-container stop depending on webbrowser-app.