madwifi-ng packages...

[Kel Modderman]

Thomas Creutz wrote:

CC'ing the pkg-madwifi list.

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>  
> Hi Kel!
>
> I happy to see, that some one debianizied the madwifi-ng sources.
>
> But i see, that you changed some thinks, thats not so a good idea.
>
>   
>> Remove madwifi-ng-dev, it is not satisfying any build dependency.
>>     
>
> I hafe it used, to build the wpa_supplicant packages.
>   

You can use the madwifi source tarball directly. This would require one 
more step (unpacking), but since madwifi-ng can now use the wext driver 
backend for wpa_supplicant, this is becoming a null point.

madwifi-ng-dev is non-free and it is not going to be used as a build-dep 
by wpasupplicant or hostapd, therefore there is no point in its existence.

Previously I argued that it existed out of convenience, but the 
maintenance overhead is not worth it once the above points are considered.

Also, when madwifi-ng hits unstable, wpa_supplicant can then include the 
madwifi-ng development headers for compilation.

>   
>> Rename source package to madwifi.
>>     
>
> The Source package name should be madwifi-ng for the existence to the
> old madwifi sources.
>   

I don't what to go back, as an upstream madwifi developer/admin, I have 
a pretty good idea of what is going on (madwifi-ng will eventually be 
named madwifi again). madwifi-old is becoming ancient history, 
*rapidly*. Soon it will be so far out of maintenance that it will fail 
to work on recent linux kernels (unless some help and time to fix it 
becomes available).


> I would love it, when you can change this back, in your next release.
>
>   


Lets see what other people watching this list think, I am open to 
suggestions/discussion.

Kel.