Add safety logic to EXTENSION scripts to avoid misuse

[strk]

Nobody should be allowed to CREATE FROM UNPACKAGED when target version doesn't match installed version. We should add version checkers in the scripts to do that.

Not sure if this means having versioned "unpackaged" files, but I guess that's the case. Maybe version for "unpackaged" could only include Major.Minor numbers.

[strk]

See also ​http://lists.osgeo.org/pipermail/postgis-devel/2013-October/023805.html

[robe]

I don't think you can do that because then you can't upgrade it.

I think you just have to in the unpackaged script run the check script version and return an error if it fails. Since the package scripts are run in a transaction, I think the script will just bail out.

In theory this should be pretty much a non-issue if done right, because since we add new functions on each minor, the unpackaged script for the current version would fail anyway because it would try to add a function not in current users install and then bail when it can't find it.

[robe]

I should add the check is really more need for micros. People saying they are running 2.1.1 when they are running 2.1.0

[strk]

bump

[robe]

Milestone renamed

[strk]

This is now deprecated because we now upgrade as part of unpackaged—version