[Monetdb-developers] New "testing" CVS module
Dear fellow MonetDB developers,
I just separated the MonetDB testing tools (Mtest.py & friends)
from MonetDB/src/testing/
into their own "testing" CVS module / MonetDB component.
IMPORTANT NOTE:
===============
In case you plan to upgrade your exiting CVS-based "MonetDB" installation,
please run `make uninstall` in your "MonetDB" build directory, first, i.e.,
before running `cvs update` in your "MonetDB" source directory.
Once you update your "MonetDB" to the latest CVS development trunk version,
and plan to continue (or start) using Mtest.py, you also need to check out
the new "testing" CVS module (from SF) and compile and install it any time
after you compiled and installed "MonetDB", and before you plan to use
Mtest.py.
The new "testing" CVS module depends only on "MonetDB" (and hence requires
that to be installed), but on no other MonetDB component (except from the
"buildtools", in case your are compiling from CVS sources).
No other MonetDB component depends on the new "testing" CVS module other
than that you obviously need to have "testing" installed once you want/need
to run tests using Mtest.py.
Details:
--------
The MonetDB testing tools (Mtest.py & friends) are not part of the actual
MonetDB functionality, but mainly for MonetDB development purpose (and hence
only distributed only in the source tarballs, but not in any (official)
binary packages).
To make them less dependent on release cycles (and vice versa), and well as
to prepare making them usable without MonetDB --- for now, they actually
still depend on MonetDB; see below) --- we decided to separate the MonetDB
testing tools from the "MonetDB" CVS module into their own "testing" CVS
module.
For the time being (i.e., until further notice), "testing" depends on
"MonetDB" --- more precisely only on some utils from MonetDB/src/common/,
but not on the GDK kernel from MonetDB/src/gdk/, as
(1) Mtest.py (mainly for "convenience") still uses monet_options.py; and
(2) (on Windows only), Mdiff.c uses "our" getopt code.
Python modules "subprocess26.py" & "trace.py" have been moved from
Dear fellow MonetDB developers,
I just separated the MonetDB testing tools (Mtest.py & friends) from MonetDB/src/testing/ into their own "testing" CVS module / MonetDB component.
IMPORTANT NOTE: ===============
In case you plan to upgrade your exiting CVS-based "MonetDB" installation, please run `make uninstall` in your "MonetDB" build directory, first, i.e., before running `cvs update` in your "MonetDB" source directory.
I also had to do ./de-bootstrap and ./bootstrap in MonetDB source directory. The remainder worked fine for me, Milena
Once you update your "MonetDB" to the latest CVS development trunk version, and plan to continue (or start) using Mtest.py, you also need to check out the new "testing" CVS module (from SF) and compile and install it any time after you compiled and installed "MonetDB", and before you plan to use Mtest.py.
The new "testing" CVS module depends only on "MonetDB" (and hence requires that to be installed), but on no other MonetDB component (except from the "buildtools", in case your are compiling from CVS sources). No other MonetDB component depends on the new "testing" CVS module other than that you obviously need to have "testing" installed once you want/need to run tests using Mtest.py.
participants (2)
-
Milena.Ivanova@cwi.nl
-
Stefan Manegold