[pkg-wpa-devel] Recent events

[Kel Modderman]

Reinhard Tartler wrote:
> On Tue, Jun 13, 2006 at 09:31:23AM -0400, Kyle McMartin wrote:
>   
>> On Tue, Jun 13, 2006 at 11:38:28PM +1000, Kel Modderman wrote:
>>     
>>> Well, we have now a pretty cutting edge in the unstable branch 
>>> (0..5.3+20060522-2) that breaks support for madwifi.
>>>
>>>       
>> If this isn't what we want, I can upload the 0.4-branch with an
>> epoch set so it will supersede the accidental upload of 0.5-branch...
>>
>>     
> We decided that we want to try the 0.5 branch in unstable for a couple
> of reasons. The most important one is that we don't want to release with
> madwifi-old support. That branch has been deprecated upstream, and
> nobody is really willing to support it any longer. Since there are still
> ppl with madwifi-old (mostly because of the fact that madwifi-old is in
> debian, and madwifi-ng not yet, but Kel told me that it will be uploaded
> today). 
>   

Not today, but ASAP. In the meantime, I have always been providing debs 
via Kanotix repository.

http://madwifi.org/wiki/UserDocs/Distro/Debian/MadWifing#DebianMadWifingPackages

> Other reason is that we believe the 0.5 branch should be mature enough
> for etch. We haven't heard about big problems on the hostap list, and
> the hostap package itself is shipping the 0.5 branch as well.
>
> On the other hand, 0.5 is still regarded as development branch upstream,
> and Jouni recommends the 0.3 or 0.4 branch for production use. This
> would speak for reverting to 0.4 with an epoch.
>
> Therefore we decided to prepare another upload of wpasupplicant of the 
> 0.5 branch with updated README.Debian which explains the situation with
> advertisment where to get madwifi-ng NOW. Moreover, the new package will
> contain both madwifi-ng and madwifi-old headers, with a switch in
> debian/rules, defaulting to madwifi-ng. If someone needs madwifi-old
> headers, he has basically 2 options: stick with the old package, or
> recompile the debian package.
>   

Just one request, please try your hardest to not say "-ng" too much. At 
madwifi.org, we are trying to eliminate that name to avoid confusion, 
and the next madwifi upload to debian will just be "madwifi", not -ng. 
Try to refer to it as the "current" driver.

> We want to try this for about a week and wait for
> comments/flames/bugreports. Then we reconsider if we should revert to
> wpasupplicant 0.4 again or stay with the 0.5 branch.
>
> I will have the package prepared in a few hours, I'm currently at work.
> If you object to this plan, and prefer to stay with 0.4, then please
> contact me. 
>
>   


Thanks very much.

I've imported the 0.5 branch into trunk, and mv'd old trunk to 
branches/wpasupplicant-0.4.

Kel.