[Pkg-octave-devel] octave3.0 build-depends versue octave3.0-headers depends

Thomas Weber thomas.weber.mail at gmail.com
Wed Dec 3 07:15:40 UTC 2008


Am Dienstag, den 02.12.2008, 23:00 +0100 schrieb Rafael Laboissiere:
> * Thomas Weber <thomas.weber.mail at gmail.com> [2008-12-02 22:38]:
> 
> > octave3.0 has quite some build-dependencies that are not mentioned in
> > octave3.0-heaers. Should we add them there?
> 
> I may be missing something but this does not seem to have been an issue up
> to now.  All packages build-depending on octave3.0-headers are correctly
> built by the autobuilders.  Hence, I do not see the need for adding extra
> dependencies to octave3.0-headers.

It's currently an issue on the octave-forge list[1]: the 'arpack'
packages needs suitesparse, but doesn't say so in its DESCRIPTION file.
The question is: should octave3.0-headers pull that in, because
octave3.0 uses it?

[1] You don't think I'm looking for virtual problems, do you? :)

	Thomas




More information about the Pkg-octave-devel mailing list