Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 24 Nov 2013 14:08:50 -0800
From:      Garrett Cooper <yaneurabeya@gmail.com>
To:        Julio Merino <julio@meroh.net>
Cc:        freebsd-testing@freebsd.org
Subject:   Re: Confusion over BSD.tests.dist
Message-ID:  <E9B8E13C-1679-4507-8949-BF8F48102E53@gmail.com>
In-Reply-To: <CADyfeQVxJbX7uRWtOhCsBNQdZ7=qnwH=s7QCYWQbq%2BLO4E%2BESg@mail.gmail.com>
References:  <83E6FED5-2E76-4E43-9547-C0DC1C90DBBD@gmail.com> <AD5A2A2F-DC12-4DBC-8E63-9EC7A872B7B7@gmail.com> <CADyfeQVxJbX7uRWtOhCsBNQdZ7=qnwH=s7QCYWQbq%2BLO4E%2BESg@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On Nov 24, 2013, at 2:04 PM, Julio Merino <julio@meroh.net> wrote:

> On Sun, Nov 24, 2013 at 5:02 PM, Garrett Cooper <yaneurabeya@gmail.com> wrote:
>>        Forwarding this message to freebsd-testing for others to have context in terms of what I’m proposing be done.
>> Thanks!
>> -Garrett
>> 
>> Begin forwarded message:
>> 
>>> From: Garrett Cooper <yanegomi@gmail.com>
>>> Subject: Confusion over BSD.tests.dist
>>> Date: November 24, 2013 at 2:01:25 PM PST
>>> To: Julio Merino <julio@meroh.net>
>>> 
>>> Hi Julio,
>>>      I think there’s some confusion over what the intent of this file was. I originally planned for it to be strictly for tests, and it seems to have morphed into a tests and test infrastructure mtree file. This is mostly ok, except for the fact that now if I specify TESTSBASE != /usr/tests, things will fail in the build.
>>>      I’d like to fix this, but that means that the ATF/Kyua infrastructure pieces really need to be moved out into their own mtree file. Does that sound ok?
> 
> Is TESTSBASE supposed to be customizable?  (And before answering that:

It can be:

# grep -r TESTSBASE share/mk
share/mk/bsd.README:TESTSDIR	Target directory relative to ${TESTSBASE} for tests and
share/mk/bsd.own.mk:TESTSBASE?= /usr/tests

> are things like LIBDIR or INCLUDEDIR user-tunabale?)

Those are user tunable too, but generally not tweaked, except when dealing with packages that use bsd.*.mk (e.g. ports):

# egrep --include \*.mk -r '^INCLUDEDIR|^LIBDIR' share/mk
share/mk/bsd.own.mk:LIBDIR?=	/usr/lib
share/mk/bsd.own.mk:INCLUDEDIR?=	/usr/include

Cheers!
-Garrett


Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E9B8E13C-1679-4507-8949-BF8F48102E53>