From owner-freebsd-ports@FreeBSD.ORG Mon Nov 10 06:26:56 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 2267CA9B for ; Mon, 10 Nov 2014 06:26:56 +0000 (UTC) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (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 D9EE172 for ; Mon, 10 Nov 2014 06:26:55 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.82 (FreeBSD)) (envelope-from ) id 1XniRA-000JV7-Qq; Mon, 10 Nov 2014 07:26:52 +0100 Date: Mon, 10 Nov 2014 07:26:52 +0100 From: Kurt Jaeger To: Joseph Mingrone Subject: Re: comments for a pmake newb Message-ID: <20141110062652.GT66862@home.opsec.eu> References: <86a93zpzz6.fsf@gly.ftfl.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86a93zpzz6.fsf@gly.ftfl.ca> Cc: freebsd-ports@freebsd.org 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: Mon, 10 Nov 2014 06:26:56 -0000 Hi! > I'm porting a program that uses a simple GNU make file, but I'm thinking > about replacing the make file to remove the devel/gmake dependency. I > don't foresee many upstream changes that will make this an issue. Is > this a bad/good idea? If the Makefile is pretty static and not changing much, one can do that. But as upstream will probably never integrate that change, what's the point ? Is the devel/gmake dependency that 'bad' ? This probably depends on the application being ported, so: What do you port ? -- pi@opsec.eu +49 171 3101372 6 years to go !