Updates in svn

[Loïc Minier]

        Hi,

On Wed, Mar 29, 2006, Kel Modderman wrote:
>    * wpasupplicant would require an update to include support for
>      madwifi-ng, and that would not *not* be compatible with a madwifi
>      interface using older drivers, however is am co-maintainer of
>      wpasupplicant, and have been modifying it locally to support
>      madwifi-ng for a long time

 Ok, of what I understood of wpasupplicant, it has various
 backends/drivers: do you think it would be possible to introduce a new
 madwifi-ng backend to stay compatible for a while with the old madwifi,
 or is it simply not worth it?  In both cases, I could imagine a
 madwifi-ng and a madwifi-ng-enabled wpasupplicant sitting in
 experimental quite soonish.

>    * same situation for hostapd, although that maintainer has already
>      included madwifi-ng headers in spite of the madwifi version
>      actually in debian. To make things worse, the headers he includes
>      have changed in upstream madwifi . . . It would also require an
>      update to work 100% with current madwifi-ng

 Ok, this is one point that will need to be addressed when madwifi-ng is
 to be uploaded to unstable.

>    * kismet would also require a svn patch/update to work with
>      madwifi-ng, although, i believe kismet has planned to better
>      support madwifi-ng in the near future (maybe a new release too)

 Same question as for wpasupplicant, would it be possible to support
 both interfaces (without too much work)?

> It'd be absolutely fantastic to upload it to experimental (right now 
> even!)

 Ok, I'm putting that on my TODO list.  Perhaps the ftpmasters won't
 like having two source packages, in which case I will rename it.

 Thanks for the information.

   Bye,

-- 
Loïc Minier <lool at dooz.org>
Current Earth status:   NOT DESTROYED