From owner-svn-ports-head@FreeBSD.ORG Wed Sep 4 13:31:04 2013 Return-Path: Delivered-To: svn-ports-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7FF62CB0; Wed, 4 Sep 2013 13:31:04 +0000 (UTC) (envelope-from stephen@missouri.edu) Received: from wilberforce.math.missouri.edu (wilberforce.math.missouri.edu [128.206.184.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4842F246D; Wed, 4 Sep 2013 13:31:03 +0000 (UTC) Received: from [128.206.184.213] (wilberforce.math.missouri.edu [128.206.184.213]) by wilberforce.math.missouri.edu (8.14.6/8.14.6) with ESMTP id r84DUT3B034897; Wed, 4 Sep 2013 08:30:29 -0500 (CDT) (envelope-from stephen@missouri.edu) Message-ID: <522735F4.9060601@missouri.edu> Date: Wed, 04 Sep 2013 08:30:28 -0500 From: Stephen Montgomery-Smith User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130816 Thunderbird/17.0.8 MIME-Version: 1.0 To: marino@freebsd.org Subject: Re: svn commit: r326241 - head/math/octave-forge-odepkg References: <201309040138.r841cHYC074414@svn.freebsd.org> <20130904033030.GC71557@FreeBSD.org> <5227293D.30108@missouri.edu> <52272A7E.2060409@marino.st> In-Reply-To: <52272A7E.2060409@marino.st> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: svn-ports-head@freebsd.org, Alexey Dokuchaev , svn-ports-all@freebsd.org, Stephen Montgomery-Smith , John Marino , ports-committers@freebsd.org X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.14 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: Wed, 04 Sep 2013 13:31:04 -0000 On 09/04/13 07:41, John Marino wrote: > On 9/4/2013 14:36, Stephen Montgomery-Smith wrote: >> >> However, from a philosophical point of view, if a project external to >> FreeBSD makes source code that is not safe for the -j option to be used, >> should FreeBSD ports committers feel that it is our job to correct their >> source code? >> >> I think the answer should be "no," and it seems you disagree. I would >> like to hear what other people think. >> > > Often issues like this are due to upstream not really understanding how > g/make works and when somebody points out issues and suggests a fix, the > fix is often taken with gratitude. > > In general I agree with you, but if the fix is trivial, why not to try > to push it back upstream? OK, what I will do is to first try to understand how gmake -j works. Then look for a fix. Then see if they want it upstream. But it will probably take me a while to get it all done.