This happens in HEAD and 0.6.2:

When installing a new tracker home the file
TEMPLATE-INFO.txt gets copied to that new directory by
roundup.init.install().

Templates are searched for in the following directories:
 1. <prefix>/share/roundup/templates/*
 2. <roundup.admin.__file__>/../templates/*
 3. <current working dir>/*
 4. <current working dir>

If the current working directory contains a tracker
home when installing a new one, it will be used as a
template, even though it's the third rule and
<prefix>/share/roundup/templates/* contains a template
of the same name.

Logged In: YES 
user_id=469548

Yes, the directories that get searched first have the lowest
precedence. I don't think this should be changed. I've
clarified the docstring to reflect this though.

Anyway, that doesn't really address the bug. I think the
correct way of resolving it is just not copying
TEMPLATE-INFO.txt to a new tracker home, but I'm not exactly
sure what Richard wants with TEMPLATE-INFO.txt. Richard, are
you okay with not copying TEMPLATE-INFO.txt?

Logged In: YES 
user_id=6405

I don't see this as an issue. It might be *useful* to keep the 
template-info file around, in case there's a link in there to get updates to 
the template. 

Logged In: YES 
user_id=839582

Yes, it _might_ be useful, but it _is_ dangerous. I didn't
describe a theoretical problem here, but a problem which
occured to me while I was installing a new tracker instance.
The main cause for this is search rule 3, which is somehow
surprising. Imagine having "./*" in your shell search path,
which is even worse than having "." in the search path like
in DOS/Windows.

I see two solutions for this issue if TEMPLATE-INFO.txt
should be in the instance home:
1. remove search rule 3 or
2. automatically change TEMPLATE-INFO.txt when being
installed to append something to the "Name:" line. Maybe
"Name: classic-foobar" if the tracker home is
"/path/to/foobar". This way you can say: Hey, I want a
tracker configured like this installed one, which of course
changes TEMPLATE-INFO.txt:Name to "classic-foobar-baz".

Now that I've written it down, the second solution sounds
really good. Should I implement it?

Logged In: YES 
user_id=6405

That does sound really good. Append "-<tracker name>" for each 
tracker the TEMPLATE-INFO passes through... Yes, please implement it 
:) 
 
Note that TEMPLATE-INFO is intended to be rfc822 parseable, so you 
should be able to just use the rfc822 Message to generate the file by 
shoving "headers" into it. 
 

Logged In: YES 
user_id=6405

Sorry, went ahead and did this cos it was kinda fun :)