Should roundup-admin reopen the tracker on every command?

Hi all:

I came across a wierd crash/error today in roundup-admin. I fixed the
underlying error caused by my incorrectly re-initializing/resetting
option validation (changeset: 7251:ab0ea9f03866) when parsing the
config.ini configuration.

However, I noticed that roundup-admin in interactive mode reopens the
tracker for every command. On the first admin command, it opens the
tracker and the database. It then caches the database handle so it is
opened only one while roundup-admin is running.

Can anybody come up with a reason the tracker needs to be reopened
every time? I would like to cache the tracker instance.

This would eliminate reparsing the configuration for every command,
and I don't think it has any downside. But I am not sure about that.

Thoughts?

--
				-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.