[Pkg-octave-devel] octave2.1-forge ready?

[Thomas Weber]

Am Mittwoch, 18. Juli 2007 13:48:12 schrieb Cyril Brulebois:
> Thomas Weber <thomas.weber.mail at gmail.com> (18/07/2007):
> Thanks, I already noticed this one, through #423993. But I don't see the
> point in not fixing the easy FTBFS, which should be quite easy (if one
> doesn't consider my question at the bottom of this mail). Instead, I'd
> be inclined to fixing the bug, and opening a dummy bug to ensure the
> package doesn't migrate to testing.

It's not that easy. There were some changes to Octave 2.9 since the release of 
octave-forge which we have in the archive. Rafael tried to get 
octave2.9-forge compiled against 2.9.10 (IIRC) and met several problems.

> Just to get the idea:
> | # wget+gunzip
> | $ grep-dctrl -F Build-Depends "octave2.1-headers" -s Package <
> | ../../Sources 
> | Package: h5utils             [y] 
AFAIK, this ships an .oct file for loading hdf5 files into Octave. Last I 
looked (long ago), I couldn't get it to work. I don't know the current state 
of it.

> | Package: octave2.1-forge [x] [y]
No problem.

> | Package: octaviz         [x] [y]
The latest upstream release is meant for 2.9. I'm currently working on a 
revamp of its build system, to get it built faster. This will however take 
some time.

> | Package: plplot
Currently orphaned, so bad luck. 

> | Package: semidef-oct     [x] [y]
No upstream release for 4 years. I'm not using it myself, so I can't comment. 

> | Package: shogun
> | Package: xmds
These have active upstreams, so that shouldn't be too much of a problem. It's 
not like the 2.9 series is just starting.


> Are the POD-maintained packages ready for a 2.1 to 2.9 switch?
Mostly, yes. Octaviz in its current archived version is not, but that is 
already resolved upstream.


> | $ grep -r gfortran .     \
> |
> |   | grep -v /.svn/       \
> |   | grep -v /tags/       \
> |   | grep -v changelog:   \
> |   | awk -F: '{print $1}'
> |
> | ./octave-forge/branches/2.9transition/debian/control
> | ./octave2.1-forge/trunk/debian/control
> | ./octave2.9-forge/trunk/debian/control
> | ./octave2.9/branches/etch/debian/in/control
> | ./octave2.9/branches/etch/debian/in/control
> | ./octave2.9/branches/etch/debian/rules
>
> My first guess would be that the headers are (or should be) holding the
> Depends, and are used by the other packages in Build-Depends, but I
> don't understand which tags/trunk I should be using to fix this. Any
> pointer, please?

Octave 2.1 and 2.9 have their trunk in the octave/ subdirectory. We don't do 
much development with 2.1 anymore, so we use just one changelog/trunk for 
both.

octave-forge doesn't have any Fortran files (more precisely, we don't build 
the one .f file it has; Octave has mex-support for quite some time).

	Thomas