[arch-dev-public] New core package: wpa_actiond
This is a small daemon that was originally part of autowifi. It will be a depend or optdepend on the next netcfg's auto-wireless mode. This will be a reliable wireless roaming mode. The daemon is somewhat similar to wpa_cli -a $script, but adds logging and avoids race conditions by adding a timeout on disconnection, an idea stolen from ifplugd. Is it okay to bring this to core? Dependencies are only glibc and wpa_supplicant, makedepends just gcc. Package is in testing for review.
On Sun, Sep 27, 2009 at 9:01 AM, Thomas Bächler
This is a small daemon that was originally part of autowifi. It will be a depend or optdepend on the next netcfg's auto-wireless mode. This will be a reliable wireless roaming mode.
The daemon is somewhat similar to wpa_cli -a $script, but adds logging and avoids race conditions by adding a timeout on disconnection, an idea stolen from ifplugd.
Is it okay to bring this to core? Dependencies are only glibc and wpa_supplicant, makedepends just gcc. Package is in testing for review.
Sounds fine to me. -Dan
Am Sonntag 27 September 2009 16:01:38 schrieb Thomas Bächler:
Package is in testing for review.
How should we test this? Will there be a new netcfg soon? Why not include iths in netcfg or might tis be usefull stand-alone? -- Pierre Schmitz, http://users.archlinux.de/~pierre
Pierre Schmitz schrieb:
Am Sonntag 27 September 2009 16:01:38 schrieb Thomas Bächler:
Package is in testing for review.
How should we test this? Will there be a new netcfg soon? Why not include iths in netcfg or might tis be usefull stand-alone?
1) netcfg can be -any 2) I maintain it, James maintains netcfg 3) This won't change much, no need to make a new binary each time netcfg scripts are released. 4) I also depend on this package with my autowifi package. James will bring a new netcfg beta to testing this week, or at least so he said.
On Mon, Sep 28, 2009 at 9:02 AM, Thomas Bächler
Pierre Schmitz schrieb:
Am Sonntag 27 September 2009 16:01:38 schrieb Thomas Bächler:
Package is in testing for review.
How should we test this? Will there be a new netcfg soon? Why not include iths in netcfg or might tis be usefull stand-alone?
1) netcfg can be -any 2) I maintain it, James maintains netcfg 3) This won't change much, no need to make a new binary each time netcfg scripts are released. 4) I also depend on this package with my autowifi package.
James will bring a new netcfg beta to testing this week, or at least so he said.
I've committed a netcfg PKGBUILD to svn, and uploaded a package here: http://mess.iphitus.org/netcfg-2.5.0a1-1-any.pkg.tar.gz I'll put b1 in [testing] once I complete documentation for the notable changes. James
participants (4)
-
Dan McGee
-
James Rayner
-
Pierre Schmitz
-
Thomas Bächler