I spent a couple hours this morning...

Hi Karl, et al.

I dusted off the generated options stuff and got it working
such that it passes the "make check".

It has the infrastructure in place for all the command
aliasing to work. A stub for every command is in place,
in addition to the preliminary implementations of add/update
etc. Option state can be saved in and pulled from .svnrc
files in the current directory or your home directory.
These files are sectioned as in:

  [SVN]
  <<option state that gets applied to all commands>>
  ....
  [SVN_ADD]
  <<option state that is only applied to the
  add subcommand>>
  ...
  [ etc. ]

There are three downloadable tarballs related to this, all
of them in ftp://autogen.sourceforge.net/pub/autogen/.

[[Please note corrected URL hers :-]]

svn-cl.tgz This is the svn client code, without the tests
                and without any generated sources

svn-clopts.tgz This is the generated option sources. With this,
                you do not have to have AutoGen, but you likely
                won't ever want to edit these, either. :-)

autoopts.tgz The add-in library. It may (or likely has) some
                portablility issues. It was designed to build
                portably insided AutoGen, even though I intended
                it to build outside. If you run into glitches,
                I'll fix 'em.

Converting this implementation to work like a shell ought to be
quite simple. About all that would be needed would be ``getline''
and a command line tokenizer.

I am presenting this because as progress is made with the
current setup, it becomes that much harder to plug that
work into this.
Received on Sat Oct 21 14:36:14 2006