madwifi-ng for debian

[Loïc Minier]

        Hi,

On Sat, May 27, 2006, Kel Modderman wrote:
> Madwifi.org recently announced [1] the first ever public release. And at 
> the same time madwifi-old has had its support cut. The package currently 
> in debian unstable and testing is based on the old code. I'd love to get 
> madwifi-ng accepted into testing before etch time, so that users of the 
> package will have some chance of receiving meaningful support.

 Great!

> What do we need to do to get the package in good shape for upload to 
> unstable, say in a few weeks time?

 My main concerns are:
 - package names: the packages should use the same names as in unstable
   when possible
 - regressions: I experienced a regression in what the HAL permitted me
   to do myself, I have no idea whether they are others, and I have no
   idea whether I have the right to get the features or not, nor whether
   Atheros cares about that...  So it's not clear to me whether we
   should look for regressions or simply face them because we have no
   other choice.  If we should look for them, then I'd say a call for
   testers should be made on a debian-* list.
 - transition dependencies: before upload, final review of deps so that
   upgrades automatically pull in the required packages (for example if
   the doc was in the old package, and is now split, we should think of
   suggesting or recommending the doc package etc.); conflicts and
   replaces if necessary

   Thanks for your work,
-- 
Loïc Minier <lool at dooz.org>
"You can gtk_main_run, but you can't gtk_widget_hide." --danw, 19-jul-04