Package: gdal
Version: 1.5.1-4
Severity: normal


thanks for packaging gdal.

The 1.5.1-4 upload has introduced this change:

  * [PATCH] gdalpaths.dpatch added to use the same plugins directory
    used currently in gdal-grass. It would require a much better approach
    upstream. See #2371 upstream bug. Also changed path for share dir path
    to /usr/share/gdal15.
    (closes: #481263)

Now I'm trying to write autotools support to install a GDAL plugin into
a system. Upstream documents the use of /usr/lib/gdalplugins, but after
1.5.1-4, Debian has diverged from that.  Now, I can only think of three
ways to find out whether I should install to /usr/lib/gdalplugins or

 1. Test for which of the two directories exists.
 2. Mess around with dpkg, to see if I am in Debian and what version of
    gdal is currently installed.
 3. Use /usr/lib/gdalplugins unless overridden by a new ./configure
    option (and therefore, leave it up to the user or the .deb

So, basically Debian has now diverged from upstream in a nonstandard
way, that requires all plugin install systems to have custom install
procedures especially for Debian.

Upstream has updated bug #2371 about this problem.



-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Pkg-grass-devel mailing list

Reply via email to