From owner-svn-ports-all@freebsd.org Tue Jul 3 07:49:23 2018 Return-Path: Delivered-To: svn-ports-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5AEB8102655A; Tue, 3 Jul 2018 07:49:23 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id D782872638; Tue, 3 Jul 2018 07:49:22 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yv.noip.me (c-24-4-131-132.hsd1.ca.comcast.net [24.4.131.132]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id w637nKCY021164 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 3 Jul 2018 00:49:21 -0700 (PDT) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-4-131-132.hsd1.ca.comcast.net [24.4.131.132] claimed to be yv.noip.me Subject: Re: svn commit: r473793 - in head/devel: . cwrap nss_wrapper pam_wrapper resolv_wrapper socket_wrapper uid_wrapper To: Mathieu Arnold , "Timur I. Bakeyev" Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org References: <201807030329.w633ThS8056768@repo.freebsd.org> <20180703065839.2oqenluilcdzkl6d@atuin.in.mat.cc> From: Yuri Message-ID: <2bc92a3f-371c-f0a6-dda1-ebed96617295@rawbw.com> Date: Tue, 3 Jul 2018 00:49:19 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180703065839.2oqenluilcdzkl6d@atuin.in.mat.cc> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jul 2018 07:49:23 -0000 On 07/02/18 23:58, Mathieu Arnold wrote: > Fun fact, TEST_TARGET may not do what you think it does. What it does > is tell the framework that the target to run when running `make test` is > test, which will probably fail if the TEST option is not enabled. What > you may have meant to set was TEST_TEST_TARGET, which sets TEST_TARGET > when the TEST option is enabled. The option TEST shouldn't be needed. What does it mean when the port is installed? You can have a test target without this option. Yuri