Yes, anything that will make those easier to maintain is a good idea. I think I 
was the one who originally split them up the way they are now, when I was 
adding support for the v. 7.3 gist changes... It wasn't too bad then, but it is 
getting a bit yucky now. I really don't know what options there are to help 
with this though... does m4 offer anything useful for this?

Chris

Quoting strk <strk@keybit.net>:

> The postgis*sql* files are becoming a major part
> of the distribution (as number of files).
> What about having a single sql for each postgres version ?
> Or - better - use some preprocessing to keep in common
> things that are common and spilt things that need to be
> splitted ?
> 
> I need to move geometry_column creation out of _common_
> into each of version-specific files because for PG75 there
> is no need of attrelid oid, varattnum int and stats histogram2d;
> this already happended for schema support changes (addGeometryColumn,
> dropGeoemtryColumn, fix_geometry_columns) and is getting boring.
> 
> --strk;
> _______________________________________________
> postgis-devel mailing list
> postgis-devel@postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
> 





