> Date: Sun, 4 Nov 2007 21:25:58 -0500 > From: Ben Abbott <[EMAIL PROTECTED]> > Subject: Re: [Fink-devel] SuiteSparse package (in support of Octave) > To: "Alexander K. Hansen" <[EMAIL PROTECTED]> > Cc: fink-devel@lists.sourceforge.net > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed > > > On Nov 4, 2007, at 9:23 PM, Alexander K. Hansen wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Ben Abbott wrote: >>> On Nov 4, 2007, at 8:35 PM, Alexander K. Hansen wrote: >>> >>> Ben Abbott wrote: >>>>>> I've uploaded a new Fink package for SuiteSparse to the >>>>>> package tracker. >>>>>> >>>>>> http://sourceforge.net/tracker/index.php >>>>>> >>>>>> When present during an Octave build, Octave will use >>>>>> SuiteSparse for many calculations using sparse matrices. >>>>>> >>>>>> This is my 1st attempt to creating a package. The package >>>>>> validated fine. However, I'm still expecting some things may >>>>>> need correcting or improving. >>> Is this intended to modify how octave builds? If so that's >>> contrary to Fink policy unless a separate variant of octave is made >>> to use it. >>> Modify how Octave builds? .... hmmm, depends upon perspective >>> (meaning I'm not sure). >>> The presence of SuiteSparse doesn't modify how Octave builds any >>> more than the packages for fftw, qhull, readline5, gnuplot, etc. >>> Octave would build and function fine (except for the absent >>> functionality) ... actually ... it *would* build and function if >>> not for the dependencies stated in octave.info. There is no need to >>> modify octave.info or octave.patch (names?) in order for >>> SuiteSparse components to be included in Octave's functionality. >>> When SuiteSparse is installed, Octave's usual configure process >>> will recognize that SuiteSparse is available and produce a makefile >>> that links to it. >>> Ben >> It would require a modification to the octave package or a variant, >> then. >> > > Shall I send an email to Octave's maintainer? >
Although it is difficult to tell from Alex's terse response, I think he means that a modification to the Octave package in Fink will be needed, i.e. a change to the octave.info file. I am still new to Fink and don't understand the details myself, but it looks like some packages have "variants": they are compiled against different libraries and are therefor different. Like you, I would argue that since fftw, qhull, hdf5 are not treated as variants, then suitesparse should not be treated as a variant either. Jonathan ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel