[Pkg-octave-devel] Bug#446331: Octave forge package

[Thomas Weber]

Am Freitag, den 12.10.2007, 11:30 +0200 schrieb Stefan Söffing:
> Am Freitag, den 12.10.2007, 10:22 +0200 schrieb Thomas Weber:
> > Hi, 
> > 
> > I'm closing this bug-report. It's simply not a bug in Octave or any
> > other package in Debian. Please use the pkg-octave-devel address for
> > discussing this further.
> 
> Hi, sorry for that, at this time I didn't realize that octave2.9-forge
>  was not built from the same source...

Oh. Well, the package's description should actually make this clear. We
should improve it in later packages, then.

> > It was removed, after not working for, uh, 6 months?. I think the last
> > working version of it was against Octave 2.9.9; though I may be wrong
> > here. By working I mean that it was actually compiled against the then
> > current Octave with a matching API number. This means that its .oct
> > files didn't load. The .m files might be working, though.
> > 
> > > Do I really have to install them manually from source now?
> > For the time being: yes.
> 
> Is there a chance to get this packaged in the future (sorry again, but I
> don't know the difference between the old 'monolithic' and the current
> version)?

The old packages was a normal source package (using autoconf, ...) and
consisted of lots of different subdirectories, roughly marking the
topics (ie, geometry, gsl, ...)

This has been split into lots (> 40) packages, enabling a finer
granulation. They are installed using Octave's pkg.m mechanism.

Packaging these things is on our agenda. 

	Thomas