octave-port and octave-forge
kay_lehmann at web.de
Fri Jun 13 01:57:49 PDT 2003
I have to ask some questions about octave-port. These are all issues, because
I am working on a port for octave-forge, which I am desperate for.
1. octave-port need some modification since configure-option --enable-shared
needs to be enabled in order to be able to load *.oct-files. This results in
some major changes to pkg-plist, because octave installs some shared
libraries, seems to be build more modular and needs more space to compile and
to be installed. So the question is: should this be an option for octave port
or is it okay to make it the default? If it has to be an option I, think I
need some advice on handling pkg-plist.
2. octave-forge is somehow broken on 4-stable:
2.1 One part of octave-forge installs a shell-script. The port I wrote till
now tries to strip the file during installation and fails. I don't know if
strip is really necessary for a shell-script, is it?
2.2 another part (communication) includes a perlscript, which is used to build
the texi- and info-files. This script is broken with 4-stable-perl, which
comes with base system. So should it be marked broken completly or should
there be a message that this part would not be installed with a 4-stable
sytem, while it is installed with 5.x?
The solution I wanted to choose is to simply disable problematic parts
(communication is enabled in 5.x).
Any help would be appreciated. If somebody want to take a look at
octave-modifications (Makefile and pkg-plist) are available at:
Sorry, I don't know if this diff works because I forgot to backup original
Makefile, but I think it should work.
Thanks for the answers.
More information about the freebsd-ports