[Pkg-octave-devel] Bug#452529: Bug#452529: several new upstream versions available

[Thomas Weber]

Am Dienstag, den 27.11.2007, 12:49 +1000 schrieb Mr Syed Azeezullah:
> Hello all,
> Ok, there is a `problem' I see with the package. Please do correct me if
> my understanding or statements are wrong.
> 
> Using `octave --eval "pkg install blah.tar.gz"' is the wrong way to go
> when installing octave-forge packages. End-users will need to have
> _many_ -dev packages installed to build and install the octave-forge
> package. While using octave's pkg is good enough when installing
> packages with only .m files, it is not the appropriate way to install
> packages have binary files created during install, OdePkg for example.

End users are not supposed to compile any code during deb installation.
If I remember the discussions on Octave's maintainer list correctly,
already built packages should not be rebuilt at install time. It
obviously means we can't move pkg.m into octave2.9-headers, but that
should not be such a big problem (it will just be change from "why is
mkoctfile not working with my own code" to "why is pkg.m not working
with my own packages").

Anyway, even if Ólafur's code works only for pure .m file packages, that
would be an improvement.

	Thomas