[Pkg-octave-devel] octave2.9 in sid

[Rafael Laboissiere]

* Colin Ingram <synergizedmusic at gmail.com> [2005-11-23 22:23]:

> I think this will be a big a project that is likely to break the
> repository how do you all feel about branching /package/octave-forge
> for this transition?

This is definitely a good idea.  I would like to keep the main trunk of
octave-forge in a near-releasable state because there will be many things
happening in the coming weeks related to the C++ ABI transition which
will imply new releases of octave-forge.

> p.s. are the other packages(semidef-oct, matwrap, epstk, gpc, statdataml 
> ) going to be affected by the api change.  If not can we just make all 
> unaffected packages including the new octave-forge-common package depend 
> on the octave virtual package.  I guess we could have a dependence that 
> is satisfied by either octave2.1 or octave2.9 also.  Maybe we should 
> branch the entire trunk?

Notice that the octave virtual package only exists to easy the
transitions.  Currently, only the octave2.1 source package generates a
virtual octave package.  In this case, I think that octave-forge-common
(or whichever name we choose) should depend on octave2.1 | octave2.9.

-- 
Rafael