Re: [OctDev] Octave-forge Development (fwd)

[Tom G. Smith (Smitty)]

I finally got a working octave, but only by using rpms, and even
then I had to force it it ignore dependencies.  Without --nodeps I
got this error:

        error: Failed dependencies:
                libqhull >= 0:2003.1 is needed by octave-forge-2004.02.12-2mdk

But, as you can see below, the qhull I was installing *was* >= 2003.1, and
I haven't located an rpm for a release any more recent than 2003.1-1:

        rpm -Uvh --force octave-2.1.40-4.i386.rpm
        rm -f /usr/local/bin/octave*
        rpm -Uvh --force --nodeps \
                octave-forge-2004.02.12-2mdk.i586.rpm \
                GiNaC-1.1.6-1.i386.rpm \
                qhull-2003.1-1.i386.rpm \
                cln-1.1.6-1.i386.rpm \
                cln-1.1.5-2.rh80.i386.rpm


        Preparing...       ########################################### [100%]
           1:cln           ########################################### [ 20%]
           2:octave-forge  ########################################### [ 40%]
           3:GiNaC         ########################################### [ 60%]
           4:qhull         ########################################### [ 80%]
           5:cln           ########################################### [100%]

And after many days of work, I still don't have a solution to the original
problem, namely that the researcher I'm working for wants to use delaunayn;
it still comes up missing.


---------- Forwarded message ----------
Date: Fri, 11 Jun 2004 18:44:22 +0300
From: Teemu Ikonen <address@hidden>
To: Mark P. Esplin <address@hidden>
Cc: address@hidden, "Tom G. Smith (Smitty)" <address@hidden>
Subject: Re: [OctDev] Octave-forge Development

On 11/06/04 11:14, Mark P. Esplin wrote:
> I am trying to figure out how octave-forge development works.  For the main
> part of octave, John Eaton set's the direction, adds patches etc., but how
> about for octave-forge?  When I look at the "Octave-forge developer's guide"
> at http://octave.sourceforge.net/ it has instructions for adding modules to
> octave-forge. Does each module's author maintain the module?  I probably
> don't have the ability or the time to add major modules to octave-forge, but
> I can do some bug-fixes, documentation, etc.  How would I go about doing
> that?

Octave-forge development is not very coordinated. Usually each author
maintains his/her own modules, but others are free to fix bugs, especially
when they're related to the build system or brokennes caused by the core
Octave changes. I think CVS commit access is given to anyone who wants it,
you just have to ask. The other option is to mail patches to the maintainer
of the module in question.

> > From: "Tom G. Smith (Smitty)" <address@hidden>
> > To: address@hidden
>
> > I've gotten octave-forge to compile and install on octave 2.1.57,
> > but I'm not at all sure I have anything more than compiled garbage.
> > I had to make numerous source code changes, some of which were
> > correcting simple typographical errors, so I know this code has never
> > been successfully compiled and tested.
>
> Some things in octave-forge work very well. It is a shame for the whole
system
> to be judged by the parts that don't work.

Octave and octave-forge are not very coordinated with each other either. The
core Octave is that much of a moving target, that the versions usually need
to be in sync. The version requirements can usually be found on the release
notes. I've just today compiled CVS checkout of octave-forge on a
CVS version of Octave and the sequence
./autogen.sh; ./configure; make; make install;
worked with no problems what so ever.

On the other hand, if one wants some get some work done instead of compiling
the bleeding edge stuff from CVS, I recommend the excellent Debian packages
of Octave and octave-forge.

Teemu


------------------------------------------------------------------------------
This e-mail is intended for the use of the addressee(s) only and may contain
privileged, confidential, or proprietary information that is exempt from
disclosure under law.  If you have received this message in error, please
inform us promptly by reply e-mail, then delete the e-mail and destroy any
printed copy.   Thank you.
==============================================================================



-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:  http://www.octave.org
How to fund new projects:  http://www.octave.org/funding.html
Subscription information:  http://www.octave.org/archive.html
-------------------------------------------------------------