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

[Thomas Weber]

Hi, 

Am Dienstag, den 02.05.2006, 23:34 +0200 schrieb Rafael Laboissiere:
> I just gave it a try here and the package builds smoothly in my unstable
> chroot.  However, make check failed (BTW, shouldn't we set
> DEB_MAKE_CHECK_TARGET in debian/rules?):

Yes, known. That's why it says in debian/rules:
	# run the check commands 
	# DEB_MAKE_CHECK_TARGET := check 
	# currently disabled, the checks fail with a crash!

I'm not the biggest debugging expert; Octave crashes in 'rand.oct' (from
octave-forge), I don't know why (and I did spend quite some time on it).
There are other issues (apparently regexp.cc from Octave and from
octave-forge are not compatible).
I thought about patching the batch_test.m out of the check: target, but
this would be cheating.

I asked Quentin (Fedora Core maintainer) and he said he had never run
the checks.


> I think we should set up things such that there will be unique SVN
> sources for both packages.  There must be a script, to be run after svn
> checking out, which will create the files with the version-specific
> informations like debian/control.

You mean in the same way as the in/ directory in current Octave? Fine
with me; however, I think we should handle the changelog in the same
way. I don't like the way we are mixing the changelog entries for Octave
2.1 and 2.9 currently.

For debian/rules, we can probably work with an 'include' statements for
the specific parts.


On the topic of debugging:
Is there a simple way to 'step' through an .m file? I worked on #361982
yesterday, but finding the correct file and line with the problem is a
pain, if one can only use 'keyboard'.

	Thomas