Am Mittwoch, den 03.12.2008, 08:52 +0100 schrieb Søren Hauberg:
> ons, 03 12 2008 kl. 08:45 +0100, skrev Thomas Weber:
> > Am Dienstag, den 02.12.2008, 23:01 +0100 schrieb Søren Hauberg:
> > > tir, 02 12 2008 kl. 22:54 +0100, skrev Thomas Weber:
> > > > Yes, but it's possible to compile Octave without sparse support. So
> > > > arpack is relying on a feature that might not be there. Or is
> > > > suitesparse now mandatory in Octave? Then my argument is obviously
> > > > void.
> > >
> > > Isn't the relevant question if the binary distributed by Debian is
> > > compiled against suitesparse? I mean, if the binary version of Octave
> > > that ships with Debian (and hence Ubuntu) depends on suitesparse, then I
> > > would assume that the octave-headers package would depend on the
> > > suitesparse headers.
> >
> > For someone who uses a binary distribution, yes. But what if I compile
> > it myself without sparse support (incidentally, I have such a stripped
> > down version of Octave running on tw-math.de, the reason is space)?
>
> Then I guess the problem is that I misunderstand the purpose of the
> 'octave3.0-headers' package. I thought the package added the stuff
> needed for making 'mkoctfile' work with the binary version of Octave. Is
> that the intention of the package or is it a meta-package that adds the
> dependencies needed for building Octave yourself?
No, the problem is not the octave3.0-headers package, which is a
separate discussion we are having in Debian right now. In fact, this is
more about people building everything from source, which is something
that should be _encouraged_.
The problem is: the 'arpack' packages assumes that Octave was built in a
certain way, which may or may not be the case. Building Octave without
sparse support is a valid configuration, so a package can't simply
assume that people will have built Octave with sparse support
(especially as suitesparse requires you to either build METIS first or
edit its Makefiles: we have more than one report in Octave's archive
about people failing to build suitesparse).
FWIW, we already had a bug report in Debian, asking us to let Octave
depend on about every database we have in Debian right now, for the sake
of the 'database' package.
http://bugs.debian.org/496699
If you depend on something that is not guaranteed to be in Octave,
mention it in the depends line.
Thomas
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Octave-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/octave-dev
