From owner-svn-ports-head@FreeBSD.ORG Thu Oct 30 22:30:32 2014 Return-Path: Delivered-To: svn-ports-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1A38A9AC; Thu, 30 Oct 2014 22:30:32 +0000 (UTC) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) (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 E4503BF1; Thu, 30 Oct 2014 22:30:31 +0000 (UTC) Received: from [192.168.1.35] (unknown [80.31.62.95]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id 200E4435AC; Thu, 30 Oct 2014 17:30:12 -0500 (CDT) Message-ID: <5452BBE6.2020908@marino.st> Date: Thu, 30 Oct 2014 23:29:58 +0100 From: John Marino Reply-To: John Marino User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Dmitry Marakasov , ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r371758 - in head/games/djgame2: . files References: <201410301626.s9UGQWQk014377@svn.freebsd.org> In-Reply-To: <201410301626.s9UGQWQk014377@svn.freebsd.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 22:30:32 -0000 On 10/30/2014 17:26, Dmitry Marakasov wrote: > Author: amdmi3 > Date: Thu Oct 30 16:26:32 2014 > New Revision: 371758 > URL: https://svnweb.freebsd.org/changeset/ports/371758 > QAT: https://qat.redports.org/buildarchive/r371758/ > > Log: > - Fix build by explicitly linking with -lX11 > It's great that the games@ team can manage to rescue this controversial port from the death twice, but can't find the time to address PR 194061 to answer if the port can be used at all. John