[Pkg-octave-devel] [RFU] octave3.2 3.2.0-1

[Rafael Laboissiere]

* Thomas Weber <thomas.weber.mail at gmail.com> [2009-06-06 23:27]:

> On Sat, Jun 06, 2009 at 09:14:06PM +0200, Rafael Laboissiere wrote:
> > 
> > It is clear that we must make the octave-forge packages available for
> > octave3.2.  However, I am not willing to maintain two sets of
> > octave-forge packages, one for each of octave3.0 and octave3.2.  I
> > propose to make them available for only octave3.2 (BTW, this is currently
> > the case of image, fixed, and general).
> > 
> > At any rate, I propose to keep octave3.0 in unstable/testing for users
> > who still need it (for instance, who have scripts that do not run on
> > octave3.2) and we decide later when it will be dropped.
> > 
> > Do you guys agree with this plan?
> 
> Fine with me.

Thanks for the prompt reply, Thomas.  Just to make the plan a bit more
precise, here is the rough time line of events:

1) octave3.2_3.2.0-1 is uploaded to unstable.

2) A new version of octave-pkg-dev is uploaded to unstable.  This version
   will adjust all the dependencies to octave3.2.
   
3) After the autobuilders will be done with octave3.2_3.2.0-1, we start
   uploading the octave-forge packages that will be built with the new
   version of the octave-pkg-dev package.  Some of them will probably need
   tweaks in order to work with octave3.2.

The only inconvenience to the users is that they will be forced to switch
form 3.0 to 3.2, in case they wish to use the octave-forge packages.

I do not think that we will need any Breaks/Conflicts/Replaces relationship
in the transition above.  However, if you foresee any potential breakage,
please let us discuss it right now.

-- 
Rafael