From owner-freebsd-testing@FreeBSD.ORG Mon Nov 25 01:40:05 2013 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6A63A39A for ; Mon, 25 Nov 2013 01:40:05 +0000 (UTC) Received: from mail-lb0-f177.google.com (mail-lb0-f177.google.com [209.85.217.177]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EA99621F3 for ; Mon, 25 Nov 2013 01:40:04 +0000 (UTC) Received: by mail-lb0-f177.google.com with SMTP id w7so2620336lbi.36 for ; Sun, 24 Nov 2013 17:39:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=Py8yigIf1EsDDw2nJCQabutBpkF4N4EQzU67ZzYRJ/w=; b=kxRfjMRZdoiisi3Ufe177cQAIGiMyLX6fX7jLmSyUEozuKdJgi0tI/rC6pFEzOvPkE i4pra/F+Ev2UhikszJr7zXdJTykICuLIaCA2nkc5ZIIoETbx7yFMytZpgg8nxIGAWFyl I+9M+s5toHjd/EWHi7gexNzMDsKRB2JRYPE9W7C5OZ43HBXDEfrihcSVSvTPgNC3Thp8 oLziy0Rs1YmiBe89mni9A9fesgLgU71SqYMZRWwR8suQX1J8v51XqiUG7BFaQaSo/efS GdsME1IFTVfcuKixX2pvgPqpLxVIIPzVKv+6tc4r9+QFL13nMFdgmcY8s2WsU/Joji6+ v4+g== X-Gm-Message-State: ALoCoQkDuN1/DRn2OOOlPWz/N4S4kQm0kROQyTaj+DazsPHc9dbFcG0YqpubmIPyoPa4oALI27F+ X-Received: by 10.112.136.163 with SMTP id qb3mr19323929lbb.14.1385343596561; Sun, 24 Nov 2013 17:39:56 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.168.65 with HTTP; Sun, 24 Nov 2013 17:39:36 -0800 (PST) X-Originating-IP: [108.176.158.82] In-Reply-To: <500AA3D4-6910-406A-A093-1B925DF0612D@gmail.com> References: <83E6FED5-2E76-4E43-9547-C0DC1C90DBBD@gmail.com> <500AA3D4-6910-406A-A093-1B925DF0612D@gmail.com> From: Julio Merino Date: Sun, 24 Nov 2013 20:39:36 -0500 Message-ID: Subject: Re: Confusion over BSD.tests.dist To: Garrett Cooper Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Cc: freebsd-testing@freebsd.org X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Nov 2013 01:40:05 -0000 On Sun, Nov 24, 2013 at 5:39 PM, Garrett Cooper wro= te: > On Nov 24, 2013, at 2:24 PM, Julio Merino wrote: > >> On Sun, Nov 24, 2013 at 5:08 PM, Garrett Cooper = wrote: >>> On Nov 24, 2013, at 2:04 PM, Julio Merino wrote: >>>> 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 ${TESTSBAS= E} for tests and >>> share/mk/bsd.own.mk:TESTSBASE?=3D /usr/tests >> >> I know it _can_ be, but the question is: do we want to support that as >> a use case? I'm not sure why anybody would want to move /usr/tests >> anywhere else. If there is no real reason other than "just because", >> I don't think the build system should make any accommodations to make >> it trivial. (Because if it's trivial, people _will_ move it and when >> things break, it's one more thing to support in bug reports.) > > Fair enough. The problem is that there are some organizations (like the o= ne I just left =97 EMC) that use other paths for testing (i.e. not /usr/tes= ts) because adjusting existing infrastructure to match new stuff is difficu= lt, introduces unnecessary risk, and could break generic tools. Right... so that's the use case I was looking for: organization that "cannot" change existing infrastructure to match the /usr/tests path. I don't know the details of your previous company at all, but I'm wondering if the path is the only thing that matters or it's just one tiny detail among many? I understand the use case... so the question is: is it worth supporting it (going all the way through to support this and other customizations that such scheme may require)? (Personally I tend to think it's not, but I don't have a strong opinion as long as the proposed modifications are simple enough.) --=20 Julio Merino / @jmmv