On Sunday 06 December 2009 10:53:55, Vincent Lefevre wrote: > On 2009-12-06 10:07:23 +0100, David Paleino wrote: > > On Sunday 06 December 2009 00:22:55, Vincent Lefevre wrote: > > > This isn't just a documentation problem. If such scripts are global, > > > then providing the wireless-settings.conf options beforescript, > > > afterscript, predisconnectscript and postdisconnectscript (that > > > are local) doesn't make sense. > > > > Well, I don't use those myself, but they make sense since you might want > > different scripts for different ESSIDs. > > I agree, but this is precisely my bug report: if one wants > different scripts for different ESSIDs, but these scripts are > executed globally, this no longer makes sense.
I believe that {after,before}script were not designed to point to things at /etc/wicd/scripts/ ;) > > Do you still want to split the bug instead of retitling it? > > What title do you suggest? Something like "pass proper arguments to the scripts in /etc/wicd/scripts/*/". I'd split it to file a documentation bug too, but there's already one, so let's avoid duplication :) I'd like to backport this feature from the current 1.7* branch, if that's not difficult. > What happens to the wireless-settings.conf options beforescript, > afterscript, predisconnectscript and postdisconnectscript is they > do not work? Ideally (and IMHO), they should be deprecated, and finally removed. Probably issuing big warnings in NEWS.Debian, posting on Planet, and so on. I need to talk with upstream about this issue, though. Kindly, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 ----|---- http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
signature.asc
Description: This is a digitally signed message part.