Peter Eisentraut wrote:

>Thomas Swan writes:
>>I just am really concerned about the uninstall/clean up phase and how
>>that can be done in an orderly fashion.  Unless the process can start
>>from a clean state again, then it won't be valid.
>The only clean state is if you remove the entire source tree and check it
>out again.  (Of course to save bandwidth, you copy the checked out source
>tree to a temporary location, do your testing, and then remove that
>temporary tree.)  Relying on make clean or make uninstall is flawed,
>because those are among the things you want to test.
That sounds plausible.   Should we let everything stay in the compilers
directory.   Something like the configure --prefix=$TEST_ROOT and that
way we can have the whole thing run as one user in one directory so that
system wide impact is minimal.    I guess what I'm concerned with is
running this on a clean system, and then leaving unknown artifacts
behind.   Can/does make install output each file it's copying and where
to.   Capturing that output would make life easier for clean up of
things installed outside of the work directory, and provide a more
controlled environment.

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
      subscribe-nomail command to [EMAIL PROTECTED] so that your
      message can get through to the mailing list cleanly

Reply via email to