Reini Urban writes:
norman:
does libgdal really needs libpython at all?
does it have an embedded python interpreter?
I only saw the python extension, which builds its seperate python gdal
modules. but nothing which refers to python within the library itself.
I want to remove -lpython2.3
Charles Wilson writes:
Reini Urban wrote:
I plan to ITP the following GIS packages in the next days.
Have to wait for some postgresql decisions upstream.
proj (but maybe Charles wants to keep his ITP)
geos
gdal (includes libgeotiff, ogr and a python lib)
Wait. Does gdal
Gerrit P. Haase writes:
Hallo Charles,
+1 vote from me for libgeotiff (makes 3 IIRC, please upload).
+1 vote for proj.
Would you ming to included also GEOS in this set of packages?
If so, +1 vote for geos.
Where did THIS come from? I ITP'ed these over a year ago;
Charles Wilson writes:
Ping? First posted on 8 Mar 03.
--Chuck
Not being a package maintainer I am not sure if I
have the privilige of voting on a package's acceptance
but ... as a bit of background since this package is probably
unfamiliar to most
Proj is becoming a standard library
Gerrit P. Haase writes:
Robert schrieb:
Gerrit, could you please give me a patch for the current libxml |
libxslt source packages to get the python modules going? I'd love to get
that working, and would get it incorporated upstream.
With the fix of Nicholas now, the latest version (of my
John Morrison writes:
Maybe all the packages ought to state where they originated?
FWIW this often helps :-)
% package --version
Should support for this be a requirement for all Cygwin packages ?
AFAIK it is for gnu applications
Cheers
Norman