From owner-freebsd-ports@freebsd.org Thu Mar 9 04:22:03 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 8C2A1D03475 for ; Thu, 9 Mar 2017 04:22:03 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from mail.infocus-llc.com (mail.infocus-llc.com [199.15.120.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6A5BA175E for ; Thu, 9 Mar 2017 04:22:03 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (c-75-65-60-66.hsd1.ms.comcast.net [75.65.60.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.tarragon.infocus-llc.com (Postfix) with ESMTPSA id 3vdy042xbmzvr; Wed, 8 Mar 2017 22:21:56 -0600 (CST) Received: by draco.over-yonder.net (Postfix, from userid 100) id 3vdy035TFXz3SK; Wed, 8 Mar 2017 22:21:55 -0600 (CST) Date: Wed, 8 Mar 2017 22:21:55 -0600 From: "Matthew D. Fuller" To: Bob Willcox Cc: Kevin Oberman , Freddie Cash , ports list Subject: Re: Best way to cause synth to ignore rebuilding of a port?? Message-ID: <20170309042155.GE49602@over-yonder.net> References: <20170308160420.GG22199@rancor.immure.com> <20170308195705.GI22199@rancor.immure.com> <20170308211337.GJ22199@rancor.immure.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170308211337.GJ22199@rancor.immure.com> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.8.0 (2017-02-23) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Mar 2017 04:22:03 -0000 On Wed, Mar 08, 2017 at 03:13:37PM -0600 I heard the voice of Bob Willcox, and lo! it spake thus: > > Hmm, the plugin/addon I use and would be lost without is for tab > groups. Do they still work in 52? I'm pretty sure it's 57 (or 58?) that they're getting broken. Certainly they work fine here on the current 52 out of ports. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.