octave-dev — GNU Octave developers' list

Re: [OctDev] Re: Directory Structure

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

"Matthew W. Roberts" wrote:
> 
> A few questions on the CVS directory structure.  As I understand it,
> contrib and dld at the top level are dead, right?  If so, I'll try
> and get them deleted.
> 

Yes, that would be great.

> Also, under octave there is a contrib directory.  Originally, my
> plan was to put all user-contributed scripts that are not part of
> the official octave under contrib.  This does not appear to be the
> case anymore.  Do we still need the contrib directory?

I don't think it is needed anymore. 

> 
> One more thing -- are we still planning on setting up a separate
> matcompat directory?  I'd like to upload Paul Kienzle's scripts into
> the repository.

I wouldn't use a separate subdirectory, we should merge the files in our
directory structure.
If we want to release a matcompat package we can use some Makefile magic
to bundle the appropriate files. 
Have you talked with Paul about that?

Bye Kai

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

[OctDev] Re: Directory Structure

[Matthew W. R. <ma...@le...>]

A few questions on the CVS directory structure.  As I understand it,
contrib and dld at the top level are dead, right?  If so, I'll try
and get them deleted.

Also, under octave there is a contrib directory.  Originally, my
plan was to put all user-contributed scripts that are not part of
the official octave under contrib.  This does not appear to be the
case anymore.  Do we still need the contrib directory?

One more thing -- are we still planning on setting up a separate
matcompat directory?  I'd like to upload Paul Kienzle's scripts into
the repository.

Thanks, 

Matt

On Oct 29, 2000 at 10:28:21AM, Kai Habel wrote:
> Hello Etienne,
> 
> I like your classification in numeric / non-numeric but I wouldn't use
> another level for general/specific. If we have to many subdirs in the
> future we could put the most specific in a separate subdir. For the dlds
> the same structure should be used, if needed. Ok we have so far.
> 
> scripts
>    +numeric
>        +elfun
>        +....
>    +nonnumeric
>        +strings
>        +io
> 
> dld
>    +numeric
>        +elfun
>        +....
>    +nonnumeric
>        +strings
>        +io
>   
> 
> If that's ok for you, I'll start setting it up and commiting.
> 
> Bye Kai
> -- 
> Kai Habel
> mailto:kai...@gm...
> 
> 
> _______________________________________________
> Octave-dev mailing list
> Oct...@li...
> http://lists.sourceforge.net/mailman/listinfo/octave-dev

Re: [OctDev] Re: octave.sourceforge.net

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

Hello Andy,



Andy Adler wrote:

> 
> Thanks for the help. It seems that I was just having some
> sourceforge.net wierdness. It worked after many tries.
> 
> I've uploaded the sparse stuff under octave/dld. I hope
> this is appropriate.

Hmm, I would like to put the external libs into a separate directory
(octave/lib). Or an extra module?

I have my libqhull stuff (triangulation,...) in the queue, that would
add 250k for the lib. 

We haven't disussed this before, should we put the libs into the
appropriate dld-subdir or in an extra dir?

> 
> I also have some image stuff.
> edge detection, bwfill, conv2, ginput, jpgread.
> Some of it is DLD and some is scripts.
> 
> Where should I put it in the CVS tree?
> 


I had a short discussion with etienne two weeks ago. We agreed on the
directory structure below.

> Hello Etienne,
> 
> I like your classification in numeric / non-numeric but I wouldn't use
> another level for general/specific. If we have to many subdirs in the
> future we could put the most specific in a separate subdir. For the dlds
> the same structure should be used, if needed. Ok we have so far.
> 
> scripts
>    +numeric
>        +elfun
>        +....
>    +nonnumeric
>        +strings
>        +io
> 
> dld
>    +numeric
>        +elfun
>        +....
>    +nonnumeric
>        +strings
>        +io
>   

For the dld functions I would suggest /dld/numeric/image or
/dld/nonnumeric/io (?). 
For script files use /scripts/numeric/image or /scripts/nonnumeric/io
(?)

Can you add a ChangeLog entry for your commits?


Bye Kai  


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

[OctDev] Re: octave.sourceforge.net

[Andy A. <en...@fr...>]

On Thu, 9 Nov 2000, Matthew W. Roberts wrote:
> On Nov 08, 2000 at 09:53:34PM, Andy Adler wrote:
> > I'm having trouble with sourceforge - maybe you can help.
> > I've installed all the ssh stuff, but I still can't
> > get cvs access.
> I'd guess the same thing as Kai that you need to set the CVS_RSH
> environment variable.  Also, you might want to check out TkCVS.
> I've found it to be a very nice graphical interface to CVS.
> 
> I did check your user permissions and they are the same as Kai, so
> that should not be the problem.

Thanks for the help. It seems that I was just having some
sourceforge.net wierdness. It worked after many tries.

I've uploaded the sparse stuff under octave/dld. I hope
this is appropriate.

I also have some image stuff.
edge detection, bwfill, conv2, ginput, jpgread.
Some of it is DLD and some is scripts.

Where should I put it in the CVS tree?

Thanks
_______________________________________
Andy Adler,                en...@nc...

[OctDev] Re: octave.sourceforge.net

[Matthew W. R. <ma...@le...>]

On Nov 08, 2000 at 09:53:34PM, Andy Adler wrote:
> I'm having trouble with sourceforge - maybe you can help.
> I've installed all the ssh stuff, but I still can't
> get cvs access.

I'd guess the same thing as Kai that you need to set the CVS_RSH
environment variable.  Also, you might want to check out TkCVS.
I've found it to be a very nice graphical interface to CVS.

I did check your user permissions and they are the same as Kai, so
that should not be the problem.

Matt

Re: [OctDev] Re: octave.sourceforge.net

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

Andy Adler wrote:
> 
> On Mon, 6 Nov 2000, Matthew W. Roberts wrote:
> > > I've now registered, and my username is aadler
> >
> > Your now an official repository developer.  Welcome aboard!
> 
> Thanks,
> 
> I'm having trouble with sourceforge - maybe you can help.
> I've installed all the ssh stuff, but I still can't
> get cvs access:
> 
> I type:
> 
> cvs -z3 -da...@cv...:/cvsroot/octave co octave
> aa...@cv...'s password:
> Permission denied, please try again.
> 
> I know this password is good because I can log into
> sourceforge from the web.
> 
> I'm I doing the correct cvs command?
> 
> Thanks
> _______________________________________
> Andy Adler,                en...@nc...
> 
> _______________________________________________
> Octave-dev mailing list
> Oct...@li...
> http://lists.sourceforge.net/mailman/listinfo/octave-dev
Hello Andy,

Did you export CVS_RSH=ssh ? Do you have ssh 1? 

I just tried:
cvs -z3 -dk...@cv...:/cvsroot/octave co octave 
It works fine here.
My ssh is
SSH Version 1.2.27 [i686-unknown-linux], protocol version 1.5.
Standard version.  Does not use RSAREF. 

Do you plan, adding the SuperLU lib to the repository? If so, it might
be a good idea to put it in an extra subdirectory 'octave/lib/SuperLU'. 

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

[OctDev] Re: octave.sourceforge.net

[Andy A. <en...@fr...>]

On Mon, 6 Nov 2000, Matthew W. Roberts wrote:
> > I've now registered, and my username is aadler
> 
> Your now an official repository developer.  Welcome aboard!

Thanks,

I'm having trouble with sourceforge - maybe you can help.
I've installed all the ssh stuff, but I still can't
get cvs access:

I type:

cvs -z3 -da...@cv...:/cvsroot/octave co octave
aa...@cv...'s password: 
Permission denied, please try again.

I know this password is good because I can log into
sourceforge from the web.

I'm I doing the correct cvs command?

Thanks
_______________________________________
Andy Adler,                en...@nc...

[OctDev] Re: octave.sourceforge.net

[Matthew W. R. <ma...@le...>]

> > If you want to be a developer you will need to register with
> > SourceForge and let us know your user name.
> 
> I've now registered, and my username is aadler

Your now an official repository developer.  Welcome aboard!

Cheers,

Matt

[OctDev] Re: octave.sourceforge.net

[Andy A. <en...@fr...>]

On Sat, 4 Nov 2000, Matthew W. Roberts wrote:
> > I would like to contribute my
> > octave sparse package to octave.sourceforge.net.
> > 
> > How do I go about doing that?
> 
> You can send me the source and I can upload it into the CVS tree, or
> we could add you as a SourceForge developer and you can maintain it
> yourself.
> 
> If you want to be a developer you will need to register with
> SourceForge and let us know your user name.

I like the 2nd idea. That way I can keep it up to date.
I've now registered, and my username is aadler

Thanks
_______________________________________
Andy Adler,                en...@nc...

[OctDev] Re: octave.sourceforge.net

[Matthew W. R. <ma...@le...>]

> I would like to contribute my
> octave sparse package to octave.sourceforge.net.
> 
> How do I go about doing that?

You can send me the source and I can upload it into the CVS tree, or
we could add you as a SourceForge developer and you can maintain it
yourself.

If you want to be a developer you will need to register with
SourceForge and let us know your user name.

Thanks,

Matt Roberts

[OctDev] cvs repository

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

Hello,

I looked into the cvs issue. It turns out, that removing directories is
_not_ possible. If we care we can ask the sourceforge administrator to
remove the top dirs dld and contrib. So be carefull when creating new
directories.
If you want to checkout the current repository use the octave module.

cvs -z3 -dd...@cv...:/cvsroot/octave co
octave

Bye Kai

P.S could one of the admins look at our mailing list. It doesn't seem to
be archived anymore.

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

[OctDev] removing directories from CVS

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

Hello,

I have commited some scripts to get a bit familiar with cvs. Now I have
a problem with removing the topdirs contrib and dld. I followed the
description in the cvs documentation.

Thats what I tried.

1. checkout i.e. the dld dir
cvs -z3 -dk...@cv...:/cvsroot/octave co dld 

2. cd dld

3. update using -P option 'prune'
cvs -z3 -dk...@cv...:/cvsroot/octave update -P

the subdirs are now removed at my local copy but not at the server.

How do get rid of these dirs?
Ahh I just read in the doc:

The -P option tells update to "prune" any empty directories - that is,
to remove them from the working copy. Once that's done, the directory
can
be said to have been removed; all of its files are gone, and the
directory itself is gone (from the working copy, at least, although
there is actually
still an empty directory in the repository). 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

So option -P does not work for this purpose.

More confused.
I will look at this tomorrow.


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

[OctDev] Re: Directory Structure

[Etienne G. <et...@is...>]

  Hello,

> If that's ok for you, I'll start setting it up and commiting.

  Sure, do.

  I won´t be very present in the next days, so don´t wait for me
before doing things.

  Cheers,

  Etienne

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...

[OctDev] Directory Structure

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

Hello Etienne,

I like your classification in numeric / non-numeric but I wouldn't use
another level for general/specific. If we have to many subdirs in the
future we could put the most specific in a separate subdir. For the dlds
the same structure should be used, if needed. Ok we have so far.

scripts
   +numeric
       +elfun
       +....
   +nonnumeric
       +strings
       +io

dld
   +numeric
       +elfun
       +....
   +nonnumeric
       +strings
       +io
  

If that's ok for you, I'll start setting it up and commiting.

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

[OctDev] Repository

[Etienne G. <et...@an...>]

 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").

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

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.

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.

  Cheers,

  Etienne

[OctDev] Repository

[Etienne G. <et...@an...>]

Hello,

From: Kai...@t-... (Kai Habel)
#  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

#  + matcompat
#  |    + m
#  |    | + audio
#  |    | + general
#  |    | + ...
#  |    |
#  |    + dld
#  |    |   + audio ???
#  |    |   + ...
#  |    |
#  |    + libs ???
#  |
#  + contrib
#       + m
#       | + audio
#       | + ...
#       |
#       + dld
#       |  + audio ???
#       |  + ...
#       |
#       + libs ???
#
#  As you can see I would like to separate the functions in matlab
#  compatible and noncompatible. Comments?
#
#  When we have the structure, I would like to start commiting with new
#  versions of my own scripts to get familiar with cvs.

  You mean we should decide what the subdirs are? I have something
like this (where I omit some directories that are of interest just for
me, and directories containing test functions). 

./general
./......./optim
./......./rot
./tools
./...../dumper
./...../graphics
./...../imgio
./...../...../images.all
./...../...../test_images
./...../matcompat
./...../misc
./...../strings
./...../struct
./...../vrml

  I agree that "tools" (not numeric stuff; well, graphics is numeric)
is not a pretty name, but it means what it means. Another possibility
is to clone octave's structure, which has a lot (too many?) "root"
directories :

./audio
./control
./......./base
./......./hinf
./......./obsolete
./......./system
./......./util
./elfun
./finance
./general
./image
./io
./linear-algebra
./miscellaneous
./plot
./polynomial
./quaternion
./set
./signal
./specfun
./special-matrix
./startup
./statistics
./........../base
./........../distributions
./........../models
./........../tests
./strings
./time

  Maybe a ad-hoc classification in numeric/non-numeric and in
general/specific?

                     general                      specific

  numeric            polynomials                  finance
                     optimization                 computer-vision
                     statistics                   graphics
                     elfun                        signal
                     specfun                      
                     linear-algebra
                     misc

  non-numeric        strings                      vrml
                     plot
                     img-io
                     io
                     misc
                     time

  
  and the same for dlds? 

  Cheers,

  Etienne

[OctDev] Repository

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

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

+ matcompat
|    + m
|    | + audio
|    | + general
|    | + ...
|    |
|    + dld
|    |   + audio ???
|    |   + ...
|    |
|    + libs ???
|
+ contrib
     + m
     | + audio
     | + ...
     |
     + dld
     |  + audio ???
     |  + ...
     |
     + libs ???

As you can see I would like to separate the functions in matlab
compatible and noncompatible. Comments?

When we have the structure, I would like to start commiting with new
versions of my own scripts to get familiar with cvs.

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

Re: [OctDev] uh... HELLO ?!?

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

mat...@ns... wrote:
> 
> 
> Anyway, just for the record, here's me sending out a ping into deep space.
> 
> Looking for an echo...!
> 
Hello Julian,

here is the pong. I would like to offer my help for this project.
Do you have any immediate plans? A good start would be, to move
matcompat to cvs. I have some new functions that aren't
mentioned/included in the current matcompat package.

to Matthew: could you add me to the developer list too
 
Bye Kai

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

[OctDev] Re: uh... HELLO ?!?

[Etienne G. <et...@an...>]

  Hello,

#  > There's been lots of talk recently about "THE Octave repository"
#  > for user contributions, and the fact that octave.sourceforge.net
#  > is in limbo (for unknown reasons).  (Are you guys still alive over
#  > there..?  uh..)
#
#  Still alive...
#
#  > I'd like to help kickstart this site again.  Let us know what's
#  > up.  It wouldn't be a disaster to simply start a forked
#  > sourceforge project, but it would be kind of silly for
#  > octave.sorceforge.net to be there nonetheless, but relatively
#  > inert.  It's not our preference.
#
#  No need to fork.  Let me know who wants to work on the Octave
#  Repository and I'll add them.

  Sure, me!

  Etienne

Re: [OctDev] Re: uh... HELLO ?!?

[Etienne G. <et...@is...>]

[OctDev] Re: uh... HELLO ?!?

[Matthew W. R. <ma...@le...>]

> There's been lots of talk recently about "THE Octave repository"
> for user contributions, and the fact that octave.sourceforge.net
> is in limbo (for unknown reasons).  (Are you guys still alive over
> there..?  uh..)

Still alive...

> I'd like to help kickstart this site again.  Let us know what's
> up.  It wouldn't be a disaster to simply start a forked
> sourceforge project, but it would be kind of silly for
> octave.sorceforge.net to be there nonetheless, but relatively
> inert.  It's not our preference.

No need to fork.  Let me know who wants to work on the Octave
Repository and I'll add them.

Best, 

--
Matthew W. Roberts
------------------------------------------------------------------
Structural Engineering  *  Texas A&M University  *  ma...@ta...

[OctDev] uh... HELLO ?!?

[<mat...@ns...>]

To anybody out there except for Etienne and Kai and jwe,

There's been lots of talk recently about "THE Octave repository" for user 
contributions, and the fact that octave.sourceforge.net is in limbo (for unknown 
reasons).  (Are you guys still alive over there..?  uh..)

I'd like to help kickstart this site again.  Let us know what's up.  It wouldn't 
be a disaster to simply start a forked sourceforge project, but it would be kind 
of silly for octave.sorceforge.net to be there nonetheless, but relatively 
inert.  It's not our preference.

Anyway, just for the record, here's me sending out a ping into deep space.

Looking for an echo...!

jo...@us...
http://matlinks.sourceforge.net

p.s. At least grant one of us admin access/privileges so we can boot the 
repository back up again =j  (pretty please?)

[OctDev] uh... HELLO ?!?

[<mat...@ns...>]

To anybody out there except for Etienne and Kai and jwe,

There's been lots of talk recently about "THE Octave repository" for user 
contributions, and the fact that octave.sourceforge.net is in limbo (for unknown 
reasons).  (Are you guys still alive over there..?  uh..)

I'd like to help kickstart this site again.  Let us know what's up.  It wouldn't 
be a disaster to simply start a forked sourceforge project, but it would be kind 
of silly for octave.sorceforge.net to be there nonetheless, but relatively 
inert.  It's not our preference.

Anyway, just for the record, here's me sending out a ping into deep space.

Looking for an echo...!

jo...@us...
http://matlinks.sourceforge.net

p.s. At least grant one of us admin access/privileges so we can boot the 
repository back up again =j  (pretty please?)

[Octave-dev] First Message

[Matthew W. R. <ma...@le...>]

The oct...@li... mailing list is used for developers
of the GNU Octave Repository web site.

The GNU Octave Repository is intended to be a central location for
custom scripts, functions and extensions.  This site is currently under
construction. If you are interested in helping to develop this site
or if you have custom scripts to contribute, please send a message to:
cg...@us.... Help from users familiar with SourceForge
and CVS is particularly needed.

Matthew Roberts