From owner-svn-ports-all@FreeBSD.ORG Wed Sep 4 12:42:17 2013 Return-Path: Delivered-To: svn-ports-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 77731532; Wed, 4 Sep 2013 12:42:17 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4D6052FEC; Wed, 4 Sep 2013 12:42:16 +0000 (UTC) Received: from [192.168.0.20] (unknown [130.255.26.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id EE271435C7; Wed, 4 Sep 2013 07:41:53 -0500 (CDT) Message-ID: <52272A7E.2060409@marino.st> Date: Wed, 04 Sep 2013 14:41:34 +0200 From: John Marino User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Stephen Montgomery-Smith Subject: Re: svn commit: r326241 - head/math/octave-forge-odepkg References: <201309040138.r841cHYC074414@svn.freebsd.org> <20130904033030.GC71557@FreeBSD.org> <5227293D.30108@missouri.edu> In-Reply-To: <5227293D.30108@missouri.edu> X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: svn-ports-head@freebsd.org, Alexey Dokuchaev , Stephen Montgomery-Smith , svn-ports-all@freebsd.org, ports-committers@freebsd.org X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: marino@freebsd.org List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Sep 2013 12:42:17 -0000 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? John