[Pkg-octave-devel] octave-forge

[Thomas Weber]

Am Sonntag, den 16.09.2007, 14:38 +0200 schrieb Ólafur Jens Sigurðsson:
> > But again: which problem is the local compile supposed to solve?
> 
> Well, I was trying to solve the problem of not having a debian package
> for the forge, a bit megalomanic of me :-)

The idea of having octave-forge as individual packages and pkg.m was the
easy installation of packages by a local user. So, what good are
distribution packages for if you can easily do it by from inside Octave?
Like the extensions for Firefox, or whatever.


> So the problem is that to make a debian package you have to compile
> the source before it is delivered to the user? Ok, that complicates
> things a lot. But still, it is a question of knowing where to put the
> files and how to let the octave system know that they are installed.
> Do you know how to do that?

Octave checks a few paths by default. Put your files in there (pkg.m
will do this) and you are done.


> Just out of curiosity, what are the problems that you see in packaging
> the forge?

Try doing it for the 40+ packages and wait for the first change that
inflicts all packages (such as a new Octave version).
 
	Thomas