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