Your message dated Tue, 20 May 2008 15:36:24 +0200
with message-id <[EMAIL PROTECTED]>
and subject line -config belongs to -dev
has caused the Debian Bug report #364981,
regarding libgdal1-1.3.1-dev: gdal-config should be in gdal-bin package?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
364981: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=364981
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: libgdal1-1.3.1-dev
Version: 1.3.1-0.dgis.stable.2
Severity: normal

Hi,

In the 1.2.6 package "/usr/bin/gdal-config" (needed for GRASS compile) 
was provided in the gdal-bin package. With the current 1.3.1 packages
(I'm using the DebianGIS backport for Stable) it has moved to the
libgdal1-1.3.1-dev package. I thought the whole point of having a
gdal-config program was to let you know what the gdal compile 
settings were without having to have a full -dev setup in place.
Now I have to have 8 new dependant -dev packages installed just to 
know what went into the libgdal compile. :(

Can it be / should it be  moved back to the gdal-bin package?


thanks,
Hamish


-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.27-3-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages libgdal1-1.3.1-dev depends on:
ii  libc6-dev          2.3.2.ds1-22sarge3    GNU C Library: Development Librari
ii  libcfitsio-dev     2.510-1               static library for I/O with FITS f
ii  libgdal1-1.3.1     1.3.1-0.dgis.stable.2 Geospatial Data Abstraction Librar
ii  libhdf4g-dev       4.1r4-18.1            The Hierarchical Data Format libra
ii  libjasper-1.701-de 1.701.0-2             Development files for the JasPer J
ii  libjpeg62-dev      6b-10                 Development files for the IJG JPEG
ii  libpng12-dev       1.2.8rel-1            PNG library - development
ii  libsqlite0-dev     2.8.16-1              SQLite development files
ii  libtiff4-dev       3.7.2-3               Tag Image File Format library (TIF
ii  libungif4-dev      4.1.3-2sarge1         shared library for GIF images (dev
ii  libxerces26-dev    2.6.0-3               Validating XML parser library for 
ii  netcdfg-dev        3.5.0-7.1             Development kit for NetCDF.
ii  postgresql-dev     7.4.7-6sarge1         development files for libpq (Postg
ii  unixodbc-dev       2.2.4-11              ODBC libraries for UNIX (developme

-- no debconf information


--- End Message ---
--- Begin Message ---
severity 364981 wishlist
thanks

As you can see in other packages (e.g. mysql, postgresql, gtk+, ...) the
config scripts always belong to the respective -dev packages. Also
consider that many information about the package can be found in
alternative ways (see --formats) or by policy.
So I'm closing this bug, because respecting common practices is much more
important than space wasted.

-- 
Francesco P. Lovergine


--- End Message ---
_______________________________________________
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel

Reply via email to