On Thu, Mar 07, 2013 at 02:18:35PM +0800, Shu Ming wrote:
> Now, The VDSM test unit is expected to run in a un-installed enviornment
> and use hackVDSM() to fake modules importing. hackVDSM() is pretty
> tricky for other modules to be added because of the dependency order. I
> would propose to run the VDSM unit tests in a installed VDSM path which
> is the same path as other VDSM runnable binaries. By this way, we can
> abandon hackVDSM() and run the unit test normally. On the other hand,
> the VDSM building script installs the VDSM files to <home>/builder by
> default, it is reasonable to start the VDSM unit test after all parts of
> the building script finishes. Any comments about this idea?
I prefer Vinzenz's take on a git repo reorganization.
There's an ongoing attempt to reach a consensus on that, though I must
admit we are a bit stuck.
vdsm-devel mailing list