From maintainers-request at octave dot org Mon Nov 28 12:32:43 2005
Subject: Re: Dependence of octave-forge on octave version
From: "John W. Eaton" <jwe at bevo dot che dot wisc dot edu>
To: Quentin Spencer <qspencer at ieee dot org>
Cc: Rafael Laboissiere <rafael at debian dot org>,         "James R. Phillips" <antiskid56-octave@yahoo.com>,         maintainers@octave.org
Date: Mon, 28 Nov 2005 13:31:55 -0500

On 28-Nov-2005, Quentin Spencer wrote:

| As the Fedora package maintainer, I guess I should repond here as well. 
| I have always just done things the easy way, installing the files in the 
| octave-forge default locations, which causes the situation you 
| described. This means there is a new octave-forge release for every 
| octave release, though sometimes they coincide anyway. However, I see 
| that the Debian approach has some advantages, so I'm considering doing 
| the same the next time I release an octave-forge. Is there an easy way 
| of extracting the "api-v*" string from octave_config_info or something 
| like it?

2.9.x has

  octave_config_info ("localapioctfiledir")

but this is not in 2.1.x.

jwe