Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 27 Oct 2013 20:25:34 -0400
From:      Eitan Adler <lists@eitanadler.com>
To:        Julio Merino <julio@meroh.net>
Cc:        freebsd-testing@freebsd.org, Rui Paulo <rpaulo@fnop.net>, Simon Gerraty <sjg@juniper.net>
Subject:   Re: Plugging ATF tests into the build and other cleanups
Message-ID:  <CAF6rxgkEPGaM4k%2BL_EdcX0tY%2BjkfvfnkAJwCg27T5QysAJa_ig@mail.gmail.com>
In-Reply-To: <CADyfeQU7Y8APwTMDo9aTR2NUi2EBq0ytQ3QcF7Ct3xC7_BatBQ@mail.gmail.com>
References:  <CADyfeQU7Y8APwTMDo9aTR2NUi2EBq0ytQ3QcF7Ct3xC7_BatBQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Oct 27, 2013 at 6:12 PM, Julio Merino <julio@meroh.net> wrote:
> Hello!
> The one concern I have here is having to keep track of all tests in
> tools/build/mk/OptionalObsoleteFiles.inc so that setting
> WITHOUT_TESTS=no cleans up /usr/tests. This will be a pain to maintain
> and a sure source of inconsistencies. If we could special-case this to
> make it more automatic, do you have any suggestions?

Is it possible to use the list of current tests and just delete any
files which are not listed?
We would need some way to have "local" tests but that should not be difficult?


-- 
Eitan Adler



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxgkEPGaM4k%2BL_EdcX0tY%2BjkfvfnkAJwCg27T5QysAJa_ig>