[Pkg-octave-devel] Status of the octave-forge pkgs uploads

[Rafael Laboissiere]

* Thomas Weber <thomas.weber.mail at gmail.com> [2008-03-24 23:29]:

> On 24/03/08 21:38 +0100, Rafael Laboissiere wrote:
> > Three of them (fixed, octgpr, and parallel) do not build on amd64.  
> 
> fixed is maintained by David, so we should report this. 

Done [1].

[1] http://sourceforge.net/mailarchive/forum.php?thread_name=20080322120239.GE4753%40heima.gjk.dk&forum_name=octave-dev

> octgpr is maintained by Jaroslav Hajek, who is quite active, so we
> should report this too. 

Done [2].

[2] http://sourceforge.net/mailarchive/forum.php?thread_name=20080322183645.GH27937%40localhost&forum_name=octave-dev

> parallel however is considered dead by me. 

Okay, let us put octave-parallel on hold.

> > First, if we patch pkg.m, the internals of octave-pkg-dev will need to be
> > changed.  
> 
> I'd say we change octave-pkg-dev to work with extracted tarballs only.

This is what I had in mind, too.

> > Second, we cannot upload a patched octave3.0 now, otherwise we
> > will disrupt the suitesparse transition [2], which is already quite painful.
> How about adding a patched pkg.m to octave-pkg-dev? Some addpath
> fiddling should take care that the local pkg.m is preferred to the
> globally installed one on the buildd.

That's a good idea.

> This is a hack, and we should carefully check whether it's worth the
> effort.

It is not much effort, actually.  It is just about adding one more file to
octave-pkg-dev and one line to octave-pkg-dev.mk.in.  Could you please add a
patched pkg.m to SVN?  Put it directly in the trunk/ directory.

> I have lost track on the suitesparse transition -- how bad is it?

The petsc package is the main blocker now.  A new version has been uploaded
today and it mysteriously FTBFS on two arches (ia64 and powerpc) [3]. Other
blockers are openoffice.org, python-scipy, and petsc4py, which need build
on some arches (mainly hppa and mips).  I would not be surprised if this
takes one week or more to settle down.

[3] http://buildd.debian.org/~jeroen/status/package.php?suite=unstable&p=petsc

-- 
Rafael