[Pkg-octave-devel] Octave-forge for 2.9

[Thomas Weber <thomas.weber.mail@gmail.com>]

Hi, 

those of you who are subscribed to the commit list have probably noticed
that I just commited 'some' changes to to 2.9transition branch. 

It should be possible to build octave-forge against 2.9 with these
changes.

This is *not* a dual-built[1]. I had some talks with Rafael about it;
upstream is cleaning up the sources and is already relying on some
features only found in Octave 2.9. So I guess it's easier to just have
two different packages with two different upstream sources.

However, the rules file is quite generic (and CDBS-based), so we
probably can take most of it for an octave-forge2.1 package.

@Rafael: The binary package name is still octave-forge2.9; you suggested
octave2.9-forge. I don't mind the change, but thought it easier to just
check-in a version and let other people try it out. 
Do ftp-admins allow two different packages in the pool which (currently)
have the same upstream -orig tarball?


[1] If someone wants to continue with the dual-build idea, the former
revision was 597.

	Thomas