backend data base

[Joerg F. Wittenberger]

Hi there,

I'm currently looking for a trouble ticket system.  So far ditrack has
managed to assure I keep literally it on screen for several days now.

What I (as a command line guy myself) am looking for is
* a simple, yet extensible system,
* which does not depend on a certain backend data base
  (because I want to put those issues eventually into a storage backend).

Now from what I see, ditrack seems to fit both requirements.  But I
might be mistaking.  So I've got a few questions:

a) Is my understanding correct, that the role of svn
in ditrack is only to transfer the issue database to a remote location
or are those merging capabilities of svn needed as well?

b) If the latter, do you depend on svn features or could ditrack be
used with other version control systems as well?

c) If the latter, is there something like a documented/documentable
API, which I would have to adhere to, if I wanted to plug a different
backend in?

Thanks for answering

/Joerg