Re: [Pkg-grass-general] New gdal package
On Fri, 10 Dec 2004 14:44:57 +0100, Silke Reimer
<Silke.Reimer@intevation.de> wrote:
> On Fri, Dec 10, 2004 at 02:21:48PM +0100, Thomas Sondag wrote:
> > Great thanks, for fixing #278539 .
> > I recently dicover a lot of useful tools (for me) in gdal pymod dir too :
> > epsg_tr.py
> > esri2wkt.py
> > gcps2wld.py
> > gdal2xyz.py
> > gdal_merge.py
> > gdalchksum.py
> > gdalimport.py
> > pct2rgb.py
> > rgb2pct.py
> >
> > I use only pct2rgb.py and rgb2pct.py with tiff, but may be that's can be
> > useful to make another package for it ?
>
> You are of course right. I thought that I did already include them
> in one of the packages but it is not true.
>
> I am not sure whether I should
> - include it into gdal-bin and make gdal-bin dependent on
> python-gdal
> - include it into python-gdal
> - make a new package
>
> I tend to the third option. What do you think?
Silke,
My suggestion would be to put them into python-gdal. If you make
gdal-bin depend on gdal-python, then why even have a seperate
python-gdal? I would assume it exists so that folks can install
GDAL without python support.
I really thinking adding a whole package for python utility
programs is unnecessary complication but then I am a bit of
an "all-in-one" sort of guy so I might not be the best judge of
this. I certainly wouldn't want to have to click on an extra package
to get the python stuff after already installing python-gdal.
I would add that I think only the scripts normally installed by
GDAL ought to be installed into the path. There are additional
examples in gdal/pymod/examples, but they are not really
"ready to use". When they are, they should be moved up
in the upstream GDAL.
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
Reply to: