From jan-oliver.wagner at intevation.de  Fri Sep 22 09:52:40 2006
From: jan-oliver.wagner at intevation.de (Jan-Oliver Wagner)
Date: Fri Sep 22 09:52:56 2006
Subject: [Slad] SLAD Bugtracker: more components
Message-ID: <200609221152.41640.jan-oliver.wagner@intevation.de>

Hi,

I am missing the component "SLADinstaller" in the bug tracker.
Can you add it?

Best

	Jan
-- 
Jan-Oliver Wagner: www.intevation.de/~jan  | GISpatcher: www.gispatcher.de
Kolab Konsortium : www.kolab-konsortium.de | Thuban    : thuban.intevation.org
Intevation GmbH  : www.intevation.de       | Kolab     : www.kolab.org
FreeGIS          : www.freegis.org         | GAV       : www.grass-verein.de

From jan-oliver.wagner at intevation.de  Fri Sep 22 10:21:35 2006
From: jan-oliver.wagner at intevation.de (Jan-Oliver Wagner)
Date: Fri Sep 22 10:21:40 2006
Subject: [Slad] Making the SLAD installation routine robust?
Message-ID: <200609221221.36675.jan-oliver.wagner@intevation.de>

Hi,

since I experienced some situation where the SLADinstallation process hangs
and you need to kill SLADinstaller, I wonder whether it is possible
to make the SLAD installation routine return with an error _always_ when
there is _some_ problem.

I am asking this quetion for the general case because it is virtually
impossible to consider any possible problem in advance. The routine
will simply fail if conditions are bad enough. I can live with this, but
it would be absolutely cool if any type of failure or hanging could be detected
and reported back. Any chance for this?

Best

	Jan
-- 
Jan-Oliver Wagner: www.intevation.de/~jan  | GISpatcher: www.gispatcher.de
Kolab Konsortium : www.kolab-konsortium.de | Thuban    : thuban.intevation.org
Intevation GmbH  : www.intevation.de       | Kolab     : www.kolab.org
FreeGIS          : www.freegis.org         | GAV       : www.grass-verein.de