Date: Wed, 04 Sep 2013 14:41:34 +0200 From: John Marino <freebsd.contact@marino.st> To: Stephen Montgomery-Smith <stephen@missouri.edu> Cc: svn-ports-head@freebsd.org, Alexey Dokuchaev <danfe@FreeBSD.org>, Stephen Montgomery-Smith <stephen@FreeBSD.org>, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r326241 - head/math/octave-forge-odepkg Message-ID: <52272A7E.2060409@marino.st> In-Reply-To: <5227293D.30108@missouri.edu> References: <201309040138.r841cHYC074414@svn.freebsd.org> <20130904033030.GC71557@FreeBSD.org> <5227293D.30108@missouri.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52272A7E.2060409>