On 2009-12-06 11:00:59 +0100, David Paleino wrote:
> 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/ ;)
OK, I now understand. When I edited the configuration, I saw a
/etc/wicd/scripts directory (with its 4 subdirectories), which
wasn't documented, and I thought this was the configured place
for putting the scripts for the beforescript etc. options.
Indeed the documentation doesn't say how the scripts are found,
i.e. if one just specifies the name of the script (searched in
the above directories) or some absolute pathname.
> > > 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 :)
In fact my bug report seems to be due to a documentation bug. I just
wanted local scripts (and didn't even know that there were global
scripts). The documentation (man pages) needs to mention the existence
of global scripts and give more details about local scripts (specified
by absolute pathnames?). But...
> > 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.
If global scripts take arguments to identify the connection, then
this is also OK for me.
> Probably issuing big warnings in NEWS.Debian, posting on Planet, and
> so on.
Yes.
The title could be something like:
documentation of scripts configuration doesn't match the actual behavior
so that the documentation needs to be changed or the behavior... or
probably both, if local scripts disappear...
--
Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
