Bug#766746: [pkg-wpa-devel] Bug#806889: wpasupplicant: New upstream version (2.5)

2016-04-24 Thread Stefan Lippers-Hollmann
Hi Thanks for the feedback, I'm really interested in the circumstances wpa_supplicant's networkd integration is supposed to be used. On 2016-04-20, Raphael Hertzog wrote: > On Wed, 20 Apr 2016, Stefan Lippers-Hollmann wrote: > > - systemd-networkd upstream hasn't committed to a policy regarding

Bug#766746: [pkg-wpa-devel] Bug#806889: wpasupplicant: New upstream version (2.5)

2016-04-20 Thread Raphael Hertzog
On Wed, 20 Apr 2016, Stefan Lippers-Hollmann wrote: > - systemd-networkd upstream hasn't committed to a policy regarding > wireless devices, its handling might change in the future Yes, but the fact that systemd might get some native support is not guaranteed to break the setup we want to use

Bug#766746: [pkg-wpa-devel] Bug#806889: wpasupplicant: New upstream version (2.5)

2016-04-20 Thread Stefan Lippers-Hollmann
Hi On 2016-04-20, Raphael Hertzog wrote: > Hi Stefan, > > On Thu, 17 Mar 2016 03:01:21 +0100 Stefan Lippers-Hollmann > wrote: > > Given that it's opt-in, explicitly documenting this as volatile > > and potentially unsupported (in the future) might be a way out, > > but I'd still

Bug#766746: [pkg-wpa-devel] Bug#806889: wpasupplicant: New upstream version (2.5)

2016-04-20 Thread Raphael Hertzog
Hi Stefan, On Thu, 17 Mar 2016 03:01:21 +0100 Stefan Lippers-Hollmann wrote: > Given that it's opt-in, explicitly documenting this as volatile > and potentially unsupported (in the future) might be a way out, > but I'd still hate to eventually break previously working network >