[Pkg-octave-devel] r1327 - in octave-forge-pkgs: octave-communications/trunk/debian octave-control/trunk/debian octave-econometrics/trunk/debian octave-fixed/trunk/debian octave-general/trunk/debian octave-gsl/trunk/debian octave-ident/trunk/debian octave-image/trunk/debian octave-informationtheory/trunk/debian octave-io/trunk/debian octave-irsa/trunk/debian octave-linear/trunk/debian octave-miscellaneous/trunk/debian octave-nnet/trunk/debian octave-octcdf/trunk/debian octave-odebvp/trunk/debian octave-odepkg/trunk/debian octave-optim/trunk/debian octave-outliers/trunk/debian octave-parallel/trunk/debian octave-physicalconstants/trunk/debian octave-plot/trunk/debian octave-signal/trunk/debian octave-sockets/trunk/debian octave-specfun/trunk/debian octave-special/trunk/debian octave-splines/trunk/debian octave-strings/trunk/debian octave-struct/trunk/debian octave-time/trunk/debian octave-vrml/trunk/debian octave-zenity/trunk/debian

[Thomas Weber]

On 29/02/08 19:05 +0100, Rafael Laboissiere wrote:
> * Thomas Weber <thomas-guest at alioth.debian.org> [2008-02-29 17:15]:
> 
> > -Build-Depends: debhelper (>= 5), octave2.9 (>= 2.9.16), make
> > +Build-Depends: debhelper (>= 5), octave3.0, make
> 
> Could you please change this to:
> 
>     Build-Depends: octave-pkg-dev 
> 
> (see my last message to the mailing list).

How do we handle the upcoming Octave 3.1 then? I mean,
octave-pkg-dev can only depend on one of octave3.0 and octave3.1? Or are
we aiming for true dual builds (that is, one source upload produces
packages for 3.0 and 3.1 at once)?

	Thomas