Re: [OctDev] Repository

[<Kai...@t-...>]

Etienne Grossmann wrote:
> 
>  Hello again
> 
> From: Kai...@t-... (Kai Habel)
> #  Hello,
> #
> #  So, we are a few registered developers now, what are our next steps? I
> #  have reread the recent thread 'User Functions' on octave-help (~ 10.
> #  october). All seems to agree to move the matcompat scripts (assembled by
> #  Paul) to sourceforge, right?
> #
> #  First we have to setup a cvs archive structure, Here is my suggestion
> [snip]
> 
>   On that subject
> 
> 1) It would be good to offer an easy way of getting parts of the
>    repository would be useful for people who don't have CVS or don't
>    want to check out the whole repository. Like tarballs, for m-files.
>    Tarballs + Makefile for DLD functions? (I don't know how to install
>    them, except "by hand").

Sourceforge provides a daily snapshot of the cvs archive. Our address is
http://cvs.sourceforge.net/cvstarballs/octave-cvsroot.tar.gz
We can release complete tarballs from time to time. If there is demand
we can split the tarball up. For the installation we can use some
autotools magic.

> 2) On-line documentation : Could use oct2html and friends.

I would like to use texinfo, that we can easily merge scripts into
octaves main tree.
 
> 
> 3) 2.1 vs 2.0 : one directory tree for each? I use only 2.1 and don't
>    know what would run with 2.0.

Same here. I don't think we have the capacity to support both trees, so
we should focus our efforts on 2.1.

 
> 4) Test functions : there is Paul's "ftest" function. Nowadays, I use
>    scripts "test_function_name", which set an "ok" variable to 1 or 0
>    and can be more or less verbose depending on the presence of a
>    "verbose" variable. This can help make sure that changes don't
>    break things.
>

I will look at this

>   Cheers,
> 
>   Etienne
> 
> _______________________________________________
> Octave-dev mailing list
> Oct...@li...
> http://lists.sourceforge.net/mailman/listinfo/octave-dev

-- 
Kai Habel
mailto:kai...@gm...