madwifi-ng-0.9.0 was officially released on 2006-05-24: see URL. I haven't had the time to test whether simply changing version numbers in the ebuild works -- will probably try later today.
Managed to get the tools compiling after modifying the version and source-file detection code, as the official .tar.bz file on SourceForge is named madwifi-* as opposed to madwifi-ng-*. It may be worth considering resurrecting net-wireless/madwifi{,-tools} Compiling of the driver itself fails with: * Preparing ath_hal module cp -f ./../hal/public/i386-elf.opt_ah.h opt_ah.h make -C /usr/src/linux M=/var/tmp/portage/madwifi-ng-0.9.0/work/madwifi-0.9.0/ath_hal MODVERDIR=/var/tmp/portage/madwifi-ng-0.9.0/work/madwifi-0.9.0/ath_hal/../symbols modules make[1]: Entering directory `/usr/src/linux-2.6.16-gentoo-r7' CC [M] /var/tmp/portage/madwifi-ng-0.9.0/work/madwifi-0.9.0/ath_hal/ah_osdep.o HOSTCC /var/tmp/portage/madwifi-ng-0.9.0/work/madwifi-0.9.0/ath_hal/uudecode ACCESS DENIED open_wr: /usr/src/linux-2.6.16-gentoo-r7/uudecode.gcda uucode is a binary file included with the source files, and I'm not sure how we can workaround this without using -sandbox.
Created attachment 87587 [details] madwifi-ng-0.9.0.ebuild Will only compile with FEATURES="-sandbox"
Created attachment 87588 [details] madwifi-ng-tools-0.9.0.ebuild
Created attachment 88790 [details] madwifi-ng-0.9.0-r1.ebuild I changed the handling of uudecode to be as described in bug #135745.
Arg, sorry for that. I did post the wrong ebuild, the correct one can be found on http://dev.azoff.se/madwifi-ng/madwifi-ng-0.9.0-r1.ebuild
Created attachment 89761 [details, diff] A simpler work-around
When will madwifi-0.9.0 can be used? I am waiting for it :-)
MadWifi v0.9.1 released Hope it will be soon in portage!
Created attachment 90360 [details] madwifi-ng-0.9.1.ebuild updated version (uses madwifi-ng-uudecode-gcda-fix.patch). madwifi-ng-tools to 0.9.1 can just be bumped.
*** Bug 138443 has been marked as a duplicate of this bug. ***
*** Bug 138890 has been marked as a duplicate of this bug. ***
Works like a charm here. Please add it to portage soon.
I got a question. Is this madwifi-ng, but offical stable version?
(In reply to comment #13) > I got a question. Is this madwifi-ng, but offical stable version? Yes.
Can somebody tell me, whats wrong or left so that madwifi-ng-0.9.1.ebuild gets into portage?
(In reply to comment #15) > Can somebody tell me, whats wrong or left so that madwifi-ng-0.9.1.ebuild gets > into portage? I have changed the version scheme of the existing ebuilds in portage today - in preparation for adding 0.9.x. I expect it to go in within a week from now.
In reply to comment #9) > updated version (uses madwifi-ng-uudecode-gcda-fix.patch). > madwifi-ng-tools to 0.9.1 can just be bumped. > where can we find the madwifi-ng-uudecode-gcda-fix.patch file?
(In reply to comment #17) > where can we find the madwifi-ng-uudecode-gcda-fix.patch file? > see the attachment section: "A simpler work-around" or directly https://bugs.gentoo.org/attachment.cgi?id=89761
Committed to Portage tree, give it a couple of hours, thanks for all the work people :)
