Part of the change from the 1.x to 2.x version was to remove the "daemon"
mode as I expect users to explicitly choose a network, so it's no longer
appropriate to run WR in init scripts.

  Large parts of WR were re-written between v1.9.9 and v2.0.s01, but I did
not touch the debian directory contents.  So, some of the assumptions in
files in ./debian are probably no longer correct (e.g. daemon mode, file
names and locations have changed, etc.).

  I have never previously maintained a software package used in Debian and I
do not run Debian, so I am unfamiliar with the meta-data requirements.  I am
willing to host documents in the official tarball to support distributions
wishing to package WR for their users.

On Tue, Aug 4, 2009 at 1:28 AM, Patrick Winnertz <win...@debian.org> wrote:

> Hey Sean,
>
> I just prepared a upload for debian, however I noted that the
> init-script starts a gui, which is not that good as wifi-radar should
> run there as a daemon (the init script doesn't stop until you close the
> wifi-radar window).
>
> It would be cool if you could have a look for wifi-radar to prevent it
> starting the gui when running in daemon mode.
> If I have time today I'll digg into this issue.
>
> Greetings
> Winnie
>
>
>
>


-- 
Sean Robinson
WiFi Radar - http://wifi-radar.berlios.de
Python WiFi - http://pythonwifi.wikispot.org

Reply via email to