Re: [Pkg-octave-devel] Status of the octave-forge pkgs uploads
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.
octgpr is maintained by Jaroslav Hajek, who is quite active, so we
should report this too.
parallel however is considered dead by me.
> 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.
Should make life easier for everybody. I haven't looked at
octave-pkg-dev, though.
> 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.
This is a hack, and we should carefully check whether it's worth the
effort. I have lost track on the suitesparse transition -- how bad is
it?
Thomas
Reply to: