Re: Separation of scripts in octave and octave-forge

[John W. Eaton]

On  8-Oct-2007, David Bateman wrote:

| Yes this is what has been suggested. However, no one want this to be
| done before 3.0 for several reasons.. Firstly that the package manager
| is still new and we should not move functions from the core of Octave
| till the package manager is widely accepted and used. Secondly, 3.0 is
| so close that we should avoid major changes till then.. I expect
| sometime during the 3.1.x series that many functions are likely to be
| moved from Octave to octave-forge...

I agree this should be done for 3.1 or later, not 3.0.

| At that point we will have a major
| problem in that we will have to support two versions of octave-forge,
| one for the 3.0.x series and one for the 3.1.x series. For that reason
| I'd personally prefer that 3.1.x gets to a point that is a few months
| from a stable release and then move all of the functions to octave-forge
| and then only support a 3.1.x series in octave-forge.. Unfortunately I
| don't think we have enough resources to support both.

OK, I'll try to remember to discuss any movement of Octave functions
to external packages before doing it so as to cause the least
disruption.

jwe