[postgis-devel] debian package / autoconf

[strk at refractions.net]

Another thought.. the autoconf script is not complete yet
but my plan is:
	- drop requirement of pgsql source

This would make debian packaging better, right ?
Are there debian packages for up to pgsql-7.2 containing
postgresql headers ? That's the single real requirment
of current code (apart from "piggybacking" of shared
lib production rules).

--strk;

On Thu, Apr 14, 2005 at 03:36:27PM +0200, strk at refractions.net wrote:
> The debian/ subdir is huge: 2.5Mb of disk space.
> Also, it patches postgis code (regress tests code and Makefile - what for?).
> I could not produce a debian package, as it seems I'd
> need to install debian package for geos and postgresql as
> well, which I don't have handy.
> 
> I think it takes more time to include.
> 
> --strk;
> 
> On Thu, Apr 14, 2005 at 01:35:49PM +0200, Markus Schaber wrote:
> > Hi, Alex,
> > 
> > alexbodn at 012.net.il schrieb:
> > 
> > > in my ignorance, i tended to believe, that pgsql2shp (at least an older one) could serve to 
> > > cleanly "dump" the spatial enabled tables of older postgis, in order to make a migration to 
> > > version 1.0.0xx. if so, the installation script might posibly offer the user to make such an 
> > > automated migration.
> > > i would be interested whether this could really be done?
> > 
> > pgsql2shp and shp2pgsql can result in slightly changed types, and will
> > fail on datatypes that are incompatible to shape files. You will also
> > lose any information about constraints, indices, triggers and other
> > metadata.
> > 
> > However, automatic updating should be possible using pg_dump and
> > postgis_restore.pl, as described in README.postgis. This should be the
> > easiest way to upgrade a database, at least if you have enough room to
> > store the dump.
> > 
> > > it is a pleasure to work with you, and i hope to see debian as part of cvs asap. thus, users 
> > > of special debian installations could give it a try before release.
> > 
> > Strk and Paul are the ones to decide this, not me. :-)
> > 
> > Markus
> > -- 
> > Markus Schaber - http://schabi.de/
> > 
> > But hey!, Standard compliance is something we should strive for, so
> > let's try and change the Standard :-) [Alexandre Oliva, GCC Developer]
>