Merge lp:~dobey/indicator-network/lib-recommends into lp:indicator-network/15.10

WFM, what will happen if it's not there, though? Will the lib "work" without the indicator?

FAILED: Continuous integration, rev:557
http://jenkins.qa.ubuntu.com/job/indicator-network-ci/406/
Executed test runs:
    FAILURE: http://jenkins.qa.ubuntu.com/job/indicator-network-wily-amd64-ci/58/console
    FAILURE: http://jenkins.qa.ubuntu.com/job/indicator-network-wily-armhf-ci/58/console

Click here to trigger a rebuild:
http://s-jenkins.ubuntu-ci:8080/job/indicator-network-ci/406/rebuild

> WFM, what will happen if it's not there, though? Will the lib "work" without
> the indicator?

If it doesn't return appropriate error conditions without, it's a bug in the library. Recommends still pulls it in by default in the default apt config on Ubuntu though. And it pulls it into seeds, if anything seeded Recommends something. But it's obviously not necessary to be running the indicator during builds. If you do need to actually run the indicator, then you should be also installing the native indicator package in cross-compiles (but you can't run any built test binaries in that situation anyway, without emulation).

W dniu 19.01.2016 o 17:06, Rodney Dawes pisze:
> If it doesn't return appropriate error conditions without, it's a bug in the library. Recommends still pulls it in by default in the default apt config on Ubuntu though. And it pulls it into seeds, if anything seeded Recommends something. But it's obviously not necessary to be running the indicator during builds. If you do need to actually run the indicator, then you should be also installing the native indicator package in cross-compiles (but you can't run any built test binaries in that situation anyway, without emulation).

Oh yeah, sure, we're not relying on it in builds/tests, just asking.