Faidon Liambotis wrote:
Hi, Sorry for taking so long to respond to this bug report, even though I've mailed some of you in private. I wasn't sure of what to do and I was hoping that the -old/-ng situation would resolve itself with the passing of time. As madwifi upstream now recommends -ng as the stable version and considers -old as deprecated/obsolete, I've decided to support only -ng in hostapd by including the respective headers in the source package, as before. Kel, I presume that this is OK with you since you've done the same for wpasupplicant?
*Only* in experimental, madwifi-ng is not yet in the unstable archive, so I thought it would only be sensible that any userspace applications support the version of madwifi in the debian archive too.
I'm currently preparing an upload that supports the stable 0.9.0 madwifi (-ng) version. I hope that is OK with everyone.
Yes, that is fine. I am preparing the new madwifi codebase for upload to unstable this weekend (although it will rot in NEW for many weeks, I suspect). I was just kinda dumbfounded that the hostapd package dropped support for old madwifi a long time before the new codebase became usable (but I did get over it ;-), or close to being in the debian archive.
The offer still stands, I am more than happy to provide madwifi header dpatches on demand for the hostapd and wpasupplicant packages for debian.
Thanks, Kel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
