any reason for a linked statically gdalinfo?

gdal_dev_reader alessandro_amici at t...
Wed Aug 21 08:38:34 EDT 2002


hi,

> > -rw-r--r-- 1 amici amici 1308560 Aug 20 15:39 gdal-bin_1.1.7-1.1_i386.deb
> > -rw-r--r-- 1 amici amici 1605506 Aug 20 15:39 libgdal0-dev_1.1.7-1.1_i386.deb
> > -rw-r--r-- 1 amici amici 1077956 Aug 20 15:39 libgdal0_1.1.7-1.1_i386.deb
> > -rw-r--r-- 1 amici amici 47504 Aug 20 15:39 python-gdal_1.1.7-1.1_i386.deb

i forgot to mention libgdal0-dev contains all the html :)

> -rw-r--r-- 1 bgmilne adm 1775889 Aug 16 18:45 gdal-1.1.7-2mdk.i586.rpm
> -rw-r--r-- 1 bgmilne adm 41789 Aug 16 18:45 gdal-python-1.1.7-2mdk.i586.rpm
> -rw-r--r-- 1 bgmilne adm 817070 Aug 16 18:45 libgdal0-1.1.7-2mdk.i586.rpm
> -rw-r--r-- 1 bgmilne adm 1501677 Aug 16 18:45 libgdal0-devel-1.1.7-2mdk.i586.rpm
> 
> At least we settled on the same major number, what do you propose about 
> gdal-python? (In terms of keeping package names consistent?) Do you want 
> to change or should I?
> 

mm... packages names are the least 'free' thing in debian ;),
i think i have almost no other choice than what i used.
if you could change gdal-python -> python-gdal wuold be nice,
but it's up to you (don't know mandrake name policy).
moreover, i prefer gdal-bin to gdal because it is not a real
application but a collection of binaries to access the library
interface.
once more i'd prefer you to change the name, but you and paul
may very well override me :)

> 
> Could you mail the patch to me or the list?
>

after lunch (i have to figure out the best way to post patches,
any hint?)

cheers,
alessandro






More information about the Gdal-dev mailing list