Bug#862678: #862678 Drop leftover Build-Depends on network-manager-dev

2018-03-11 Thread Michael Biebl
Control: retitle -1 Switch from network-manager-dev to libnm-dev Hi Ari Am 11.03.2018 um 22:16 schrieb Ari Pollak: > On Sun, Mar 11, 2018 at 5:15 PM Ari Pollak > wrote: > > On Sun, Mar 11, 2018 at 5:00 PM Michael Biebl

Bug#862678: #862678 Drop leftover Build-Depends on network-manager-dev

2018-03-11 Thread Ari Pollak
On Sun, Mar 11, 2018 at 5:15 PM Ari Pollak wrote: > On Sun, Mar 11, 2018 at 5:00 PM Michael Biebl wrote: > >> By that I mean: If you don't have a runtime requirement, do you only use >> the D-Bus API? If so, why is network-manager-dev required as build >>

Bug#862678: #862678 Drop leftover Build-Depends on network-manager-dev

2018-03-11 Thread Ari Pollak
On Sun, Mar 11, 2018 at 5:00 PM Michael Biebl wrote: > By that I mean: If you don't have a runtime requirement, do you only use > the D-Bus API? If so, why is network-manager-dev required as build > dependency at all? > Right, it's just using the D-Bus API during runtime, but

Bug#862678: #862678 Drop leftover Build-Depends on network-manager-dev

2018-03-11 Thread Michael Biebl
Am 11.03.2018 um 21:56 schrieb Michael Biebl: > Am 11.03.2018 um 21:10 schrieb Ari Pollak: >> Pidgin is still using network-manager-dev to have NetworkManager support >> without requiring an extra runtime dependency. > > How does that work? By that I mean: If you don't have a runtime

Bug#862678: #862678 Drop leftover Build-Depends on network-manager-dev

2018-03-11 Thread Michael Biebl
Am 11.03.2018 um 21:10 schrieb Ari Pollak: > Pidgin is still using network-manager-dev to have NetworkManager support > without requiring an extra runtime dependency. How does that work? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from