[qmtest] qmtest for linux

[Stefan Seefeld]

Diana Bosio wrote:

>> as of release 2.1 qmtest has a new build system which allows you to
>> run 'python setup.py install' (and so the python tool you run during the
>> build/install will be the python tool that is used by the installed tool,
>> whether it's called 'python' or 'python2').
>>
> Thanks! From which directory shall I try to run it? From 
> /usr/lib/python2.2/site-packages/qm ? Does it go automatically to 
> /usr/local? And in any case, do I have a way to configure the target 
> directory?

The installation procedure we are talking about applies to a source distribution,
and so you run it from the toplevel (source) directory, i.e. 'qm'.
If you already have files in /usr/lib/python2.2/site-packages/qm it's
because you either installed a binary distribution or you have a previous
release there.

As to the installation location, that is usually determined by the python
interpreter (a python 2.3 installation in /usr/local would typically install
new packages into /usr/local/lib/python2.3/site-packages...).
You can override these defaults using the '--prefix' option. See
'python setup.py --help' for everything you can choose at build/installation
time (again, this has to be run in the toplevel source directory, where you
should find a 'setup.py' file).

>> However, the toplevel 'README' file still suggests to use 'configure; 
>> make install;'.
>> That appears to be a slim wrapper around the former, so I'm not sure why
>> this is still suggested, or even necessary. Mark ?
>>
> This would imply that you have a file called "configure" and another one 
> called "Makefile" at the top of the tree, but I have no such files in 
> the new version, I've tried to look in different directories, but had no 
> luck. Where did you find it?

A source distribution should contain everything you need, i.e. 'configure',
'GNUMakefile.in', 'setup.py', etc.
I suspect you are not looking at the right place.

If we are talking about a binary distribution, all files are already
in their destination directory, and thus there isn't any choice any more
as to how to call the python interpreter. Generally binary distributions
are specific to the python versions they had been compiled for.

Regards,
		Stefan