From owner-freebsd-ports@freebsd.org Thu Dec 7 02:56:43 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BCBC0E98CFE for ; Thu, 7 Dec 2017 02:56:43 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 835097199B for ; Thu, 7 Dec 2017 02:56:42 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id vB72vg07094826 for ; Wed, 6 Dec 2017 18:57:48 -0800 (PST) (envelope-from bsd-lists@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 From: "Chris H" Reply-To: bsd-lists@BSDforge.com To: "FreeBSD ports" Subject: # FLAVORLESS tag? Date: Wed, 06 Dec 2017 18:57:48 -0800 Message-Id: <404ec71b2ef09ec4d031e937e29c80c0@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Dec 2017 02:56:43 -0000 As I take inventory before embarking on "flavoring" those ports I maintain that can be flavored=2E I wanted to make my life simpler, and in an effort to do so, began tagging those that couldn't be flavored (no options, etc=2E=2E=2E) with # FLAVORLESS This made it trivial for future searches to weed out those that FLAVOR didn't apply=2E As I imagine the ultimate last minute housekeeping that will need to be done in the master ports tree; would it make it any easier to simply create a tag FLAVORLESS, for those ports that flavors do not apply? --Chris