[Pkg-grass-devel] depends problems with libgdal1-grass

Steve Halasz debian@adkgis.org
Mon, 06 Jun 2005 14:47:38 -0400


On Mon, 2005-06-06 at 17:03 +1200, Hamish wrote:
> Hi,
> 
> just updating to the new libgdal-grass_1.2.5-0.dgis.unstable.4 and I
> have a depends problem.
> 
> libgdal-grass (1.2.5-0.dgis.unstable.4) unstable; urgency=low
> 
>   * Depend on libgrass. The grass libs have no SONAMES, so the
>     dependency is not automatically included by dh_shlibdeps.
>   * Make Debian GIS Project the maintainer.
> 
>  -- Steve Halasz <debian@adkgis.org>  Fri,  3 Jun 2005 13:50:40 -0400
> 
> 
> 
> 
> libgdal-grass now depends on libgrass, and libgrass depends on grass.
> So libgdal-grass effectively depends on grass.
> 
> I thought the whole point of libgdal-grass was that you didn't need
> grass installed to read GRASS maps.

Well at least you don't need GRASS installed if you _don't_ want to read
GRASS maps :)

> 
> I only want the GDAL-grass plugin on this system. I am using a self-
> compiled GRASS version which isn't installed and only exists in /home/.
> 
> I can understand libgdal-grass depending on libgrass, but does libgrass
> really need to depend on grass?

AFAICT it does. This is why Radim includes the check for GISBASE in the
qgis plugin. The libraries are not self-contained. They make use of
various files in the GRASS installation. Of course it would be better if
the libraries could be completely separated. Maybe we can figure out
which files in the install are needed by libgrass and include those in
the libgrass package. All the stuff in /usr/lib/grass/bin
and /usr/lib/grass/man can probably be left in the grass package at
least.

Steve