Re: Octave-Forge packages and release 4.0

[Rik]

On 02/18/2015 09:00 AM, address@hidden wrote:

Subject:

Re: Octave-Forge changes for 4.0 release

From:

"Avinoam Kalma" <address@hidden>

Date:

02/17/2015 01:23 PM

To:

<address@hidden>

CC:

address@hidden

List-Post:

<mailto:address@hidden>

Content-Transfer-Encoding:

quoted-printable

Precedence:

list

MIME-Version:

1.0

Message-ID:

<address@hidden>

Content-Type:

text/plain; charset="iso-8859-1"

Message:

3

Hi,

> On 02/13/2015 09:00 AM, address@hidden wrote:

> On Thu, Feb 12, 2015 at 11:52:15PM +0000, Carnë Draug wrote:

>> Hi
>> 
>> the ismatrix function in Octave will change for the new version 4.0.
>> Currently, this function returns true if it is a numeric, logical, or
>> character array with any number of dimensions.  The new version will
>> return true if the object has two dimensions even if it is a cell or
>> struct array.
>> 
>>     WARNING: ismatrix() will return true for a struct and false for
>>             ND numeric arrays.
>> 
>> I quickly grepped Octave Forge for ismatrix and it is used in most of the
>> packages.  Would be nice if this is fixed in the packages 

> Done for optim and parallel,

>> and there were
>> new released of them before Octave 4.0.

> but no new releases yet. Is now already a good time to finally check
> packages for Octave 4.0 compatibility? Or should we take the time when
> Octaves test tarballs are out?

> You are better off to wait until the 4.0 test tarballs arrive.  I can't

say, but there > might be further changes.

> --Rik

Is it possible to build a directory for Octave 4.0 packages, and change
accordingly
the urls in get_forge_pkg.m? It will enable testing the packages with the
dev version, and fixing them if needed.

Avinoam

Octave-Forge isn't my specialty, but I think we should have some sandbox where we can test packages ahead of the 4.0 release.  In previous releases Octave core would move forward and release, and then there would be a period while the Octave-Forge developers scrambled to update their packages.  This won't work well for the 4.0 release because the intention is to ship the core and certain popular packages bundled in a single NSIS installer unit for Windows.

--Rik