Dependence of octave-forge on octave version

[James R. Phillips]

Hi,

I am preparing the new 2.1.72 octave release for cygwin.  I notice now that
most of the files in the octave-forge package are in a directory tree with the
previous octave  release version (2.1.71) encoded in the path, which means that
the octave-forge files are not (by default visible) within the new 2.1.72
release, even if they are present.

This does not seem to be the case in Debian.  So I wonder - is octave-forge
when compiled truly bound to the version of octave installed on the system at
that time?  Or would it be compatible with later versions, as long as they
maintain the same abi?

As it is, it appears I will have to release a new octave-forge version to go
with the new octave version.  Is there any easy way to prevent this happening
in the future?

Advice/comments would be appreciated.

Jim Phillips