[qmtest] running qmtest on bash in cygwin...

[Mark Mitchell]

> Does the same apply for the other sets of files ? I.e., do you want (as
> in the original setup.py file) to find all modules to install by looking
> for __init__.py files ?

I'd prefer that, but I don't think it's as important.  We add new
modules rarely, and if they're missing we'll probably notice quickly.

> fine. Do you have any other means to remember open issues (a 'TODO' file
> or something similar ?)

We do, but its internal to CodeSourcery.  Creating a TODO file at the
top level in the sources is a good idea; feel free to do that.

We keep meaning to set up a real, world-visible issue-tracker, but we
keep having more important things to do.

> The file layout in the build tree is not the same as in the source tree.
> Would you mind (eventually) refactoring the directory structure in the
> source tree to better match the installation (for example take the 
> qmtest.py script out of the modules, put resource files and even the 
> builtin 'classes' into 'share/qm/test', etc.) ?

That would be OK.  Before we do that, we should be sure that the
installation tree looks the way we want.
 
Thanks,

-- 
Mark Mitchell
CodeSourcery, LLC
mark at codesourcery.com