[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [Pkg-grass-general] Re: Bug#264566: Any progress on grass 5.7?



On Sat, Oct 09, 2004 at 08:31:55AM +0200, Francesco Paolo Lovergine wrote:
> On Sat, Oct 09, 2004 at 02:08:13AM -0400, Steve Halasz wrote:
> > Hi,
> > 
> > I have grass5.7, libgrass5.7, and libgrass5.7-dev packages in good
> > working order at:
> > 
> > deb http://bullhorn.org/debian unstable main
> > deb-src http://bullhorn.org/debian unstable main
> > 
> > A missing manpage and unstripped binary are the remaining lintian
> > errors. In other respects I think they are in good shape. There is also
> > a gdal-1.2.3 package there that works against it nicely. I haven't built
> > them with pbuilder though. I worry that circular dependencies between
> > the two will make grass build-depend on itself :-/
> > 
> 
> If Silke would keep an eye onto gdal and reports known issues about
> libray upgrade we could start to have it into experimental or pkg-grass
> staging area (to be created IMHO).

Sorry of my long absence in the discussion. I have been very busy by
preparing our presentation for the upcoming Intergeo (starting
aftertomorrow). The Intergeo is an international known GIS oriented
fair, which takes part at Stuttgart this year. 

BTW: If somebody of this list has planned to visit the Intergeo I
would be happy if he comes to our booth (B6.130) to know him
personally :-)

OK. Now back the the grass/gdal problem:
Indeed the problem is that I need the grass development package for
gdal to be build against grass. Otherwise we need gdal to build
grass with general gdal support (i.e. with support for other raster
and vector formats).

So the build order is
- create grass development libraries
- build gdal
- build grass

Since I can not make gdal build depend on grass and grass build
depend on gdal in the same time  I only see one solution to get both
pacakges in a clean way into debian:

grass is splitted into two completely independent packages. The
first one is just meant to build the development packages
(libgrass-dev) and doesn't create any binary packages at all. The
second one does build grass and libgrass.

Disadvantage:
- The grass src will be included twice in debian :-(

Other suggestions? Am I overlooking something?

Many greetings,

	Silke

-- 
Silke Reimer

Intevation GmbH                      http://intevation.de/
FreeGIS                                http://freegis.org/

Attachment: pgp5afwQc810a.pgp
Description: PGP signature


Reply to: