[postgis-devel] geos / postgis version

[strk]

I've added postgis_lib_version() and postgis_geos_version().
Before proceeding it might be worth changing geos::version()
output (and maybe name) to be able to get GEOS version only
(and geos::jtsport() addition...).

Any hint on proj4 version string extraction is appreciated
(with back-compatibility in mind).

NOTE that postgis_lib_version also reports micro version
which is actually not used in library file name (this is
built using postgresql rule, which do not take a micro version
number). Remember to upgrade SO_MICRO_VERSION between releases.

--strk;

On Thu, Jul 22, 2004 at 08:24:59AM -0700, Paul Ramsey wrote:
> I think it is wise, and you should look at one of the emails today, 
> which suggested reporting out versions of the libraries we are using 
> (geos,proj) in addition to whether we have them.
> 
> strk wrote:
> >Current postgis_version() function is implemented as a pl/pgsql
> >function. Sometimes people upgrade postgis library w/out upgrading
> >pl/pgsql functions, and this is *sometimes* a problem.
> >
> >I think it would be useful to have the following informations
> >retrivable:
> >	postgis_scripts_version();	// pl/pgsql  function
> >	postgis_lib_version();		// C function
> >	postgis_geos_version();		// C function
> >
> >Our postgis_version() would then be a wrapper, retriving the above
> >informations and warning user in case
> >postgis_scripts_version() != postgis_lib_version()
> >
> >What do you think ?
> >
> >--strk;
> >_______________________________________________
> >postgis-devel mailing list
> >postgis-devel at postgis.refractions.net
> >http://postgis.refractions.net/mailman/listinfo/postgis-devel
> 
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel