Re: [OctDev] adding ode solvers to cvs

[Paul K. <pki...@ki...>]

Marc, 

For the moment, maintain your ode functions where I have put them in
octave/contrib/scripts/ode.  The whole CVS tree needs to be periodically
replaced since CVS does not allow you to move or remove directories.
We can move the ode directory when we redo the CVS tree if you want it
somewhere else.

IMHO, any files in the main tree (presently octave/scripts) should use
Octave style.  If you want your functions to work in Matlab then you
should either keep them out of the main tree (which is why I put them
in contrib), or write them in such a way that they can be automatically
converted to Matlab.  I have an oct2mat conversion script which does this,
but you have to be careful how you write your code.

Let me know what you want to do.

The consensus reached by the early adopters of octave.sf.net is the
directory structure presently in place.  I've made a counter-proposal
neither accepted nor rejected by the original team.  In the end, it
doesn't really matter so long as the (as yet non-existing) control files
build and install things correctly, and so long as it is clear where
new files should go.

Matcompat will disappear at the end of July, so you can ignore it.
All the code is at sourceforge, but it is not yet packaged in a form
that can be easily built and installed.  Hopefully it will be packaged
properly before matcompat disappears.

- Paul

On Wed, Jun 06, 2001 at 12:15:29AM -0500, Marc Compere wrote:
> dev,
> 
> 	Ok guys, I'm ready to learn how to maintain the octave ode solvers on 
> sourceforge.  I've read some earlier postings & seen the solvers in two 
> different places.  Before I attempt to barge in and dump them somewhere, I'd 
> like to get some input on where to put and maintain the ode solvers 
> directory.
> 
> 	I'm new to cvs but can figure it out easily enough I'm sure.  Just need to 
> know what the concensus is on a directory name (like ode_solvers) & whether 
> or not they should be incorporated into matcompat (then sourceforge) or if it 
> would be better to maintain them as their own "module" under ./octave.
> 
> 	Any tips? (Paul?)
> 
> Marc
> 
> 
> -- 
> _________________________________________________
>  Marc Compere, The University of Texas at Austin
>  Com...@as..., (512) 826-0729,   <><
>  http://nerdlab.me.utexas.edu/~compere
> _________________________________________________
> 
> _______________________________________________
> Octave-dev mailing list
> Oct...@li...
> http://lists.sourceforge.net/lists/listinfo/octave-dev
>