Re: [DebianGIS] building gdal-1.3.1 packages
Jon,
On Fri, 2005-10-07 at 09:19 -0700, Jon Saints wrote:
> Thank you Frank. That was of great help.
>
> I also found this note in the pkg info for
> postgresql-dev:
>
> "The former postgresql-dev package has been split up
> into libpq-dev for client-side development and
> postgresql-server-dev-<version> packages for
> server-side development. However, this package does
> not
> depend on postgresql-server-dev-<version>."
This is not a pg server type package. postgis is an example of a package
that is a pg server extension.
>
> So, given that and Frank's information that versions
> where handled at run time I change the control file
> line:
>
> Build-Depends: debhelper (>> 4.1.25), zlib1g-dev,
> libcfitsio-dev, netcdfg-dev, libtiff4-dev,
> libjasper-1.701-dev, libpng12-dev, libjpeg62-dev,
> libungif4-dev, libhdf4g-dev, postgresql-dev,
> postgresql-client, libxerces26-dev, unixodbc-dev,
> libsqlite0-dev, python-dev, python-numeric, doxygen,
> d-shlibs, libgeos-dev
>
> to:
>
> Build-Depends: debhelper (>> 4.1.25), zlib1g-dev,
> libcfitsio-dev, netcdfg-dev, libtiff4-dev,
> libjasper-1.701-dev, libpng12-dev, libjpeg62-dev,
> libungif4-dev, libhdf4g-dev, libpq-dev,
> postgresql-server-dev-7.4 | postgresql-server-dev-8.0,
> postgresql-client-7.4 | postgresql-client-8.0,
> libxerces26-dev, unixodbc-dev, libsqlite0-dev,
> python-dev, python-numeric, doxygen, d-shlibs,
> libgeos-dev
I think libpq-dev | postgresql-dev is all that is required. Even
postgresql-client should probably be dropped. postgresql-dev is there to
ease backporting. See:
http://lists.debian.org/debian-devel/2005/06/msg00500.html
Steve
>
> With this change I was able to build and install,
> remove gdal-1.3.1 packages.
>
> Does this look good to everyone?
>
> Thanks
> Jon
>
>
>
> --- Frank Warmerdam <warmerdam@pobox.com> wrote:
>
> > On 10/7/05, Jon Saints <saintsjd@yahoo.com> wrote:
> > > This brings up an interesting question... these
> > > packages are now postgresql version specific.
> > What is
> > > the best way to deal with the new multi-posgresql
> > in
> > > terms of the gdal package? Do I need to make two
> > > gdals, one for postgres-7.4 and another for
> > > postgres-8.0?
> >
> > Jon,
> >
> > >From GDAL's point of view it can access either
> > version given
> > either version of the client libraries. That is,
> > all version
> > specific decisions are done at runtime.
> >
> > But if it came down to this, I would advocate just
> > supporting
> > the postgres 8 version. I would add if necessary we
> > could
> > have a separate gdal-postgres plugin driver like we
> > do with
> > GRASS.
> >
> > > New to packaging and I could use the opinion of
> > some
> > > experts.
> >
> > I should stress I am not a debian packaging expert.
> >
> > Best regards,
> > --
> >
> ---------------------------------------+--------------------------------------
> > I set the clouds in motion - turn up | Frank
> > Warmerdam, warmerdam@pobox.com
> > light and sound - activate the windows |
> > http://pobox.com/~warmerdam
> > and watch the world go round - Rush | Geospatial
> > Programmer for Rent
> >
> > _______________________________________________
> > Pkg-grass-general mailing list
> > Pkg-grass-general@lists.alioth.debian.org
> >
> http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-general
> >
>
>
>
> _______________________________________________
> Pkg-grass-general mailing list
> Pkg-grass-general@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-general
Reply to: