From owner-freebsd-ports@FreeBSD.ORG Wed Nov 5 22:34:43 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D013C49C for ; Wed, 5 Nov 2014 22:34:43 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8E7DB1C1 for ; Wed, 5 Nov 2014 22:34:43 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Xm99u-0003ll-Do for freebsd-ports@freebsd.org; Wed, 05 Nov 2014 23:34:34 +0100 Received: from 65.75.36.70 ([65.75.36.70]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 05 Nov 2014 23:34:34 +0100 Received: from gyliamos by 65.75.36.70 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 05 Nov 2014 23:34:34 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-ports@freebsd.org From: Will Parsons Subject: updating x11/xbindkeys for newer Tcl/Tk Date: Wed, 5 Nov 2014 22:34:18 +0000 (UTC) Lines: 13 Message-ID: Reply-To: gyliamos@gmail.com X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 65.75.36.70 User-Agent: slrn/1.0.1 (FreeBSD) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Nov 2014 22:34:43 -0000 When I went to build xbindkeys with Tcl support, I noticed it was trying to install Tcl8.4, which is quite old. Since I already have Tcl 8.5 and Tcl 8.6 installed, installing Tcl8.4 seemed to be a waste. I edited the Makefile to replace references to 8.4 with 8.5, and it seems to build correctly with the later Tcl, but it would seem be good to have the official port updated. Seeing how the maintainer is ports@FreeBSD.org (which I gather means it has no maintainer), is submitting a PR likely to get this fixed, or does it need an official maintainer first? -- Will