Date: Mon, 23 Jun 2014 13:49:33 -0700 From: Eitan Adler <eadler@freebsd.org> To: Alexey Dokuchaev <danfe@freebsd.org> Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, marino@freebsd.org, Oliver Lehmann <oliver@freebsd.org>, ports-committers@freebsd.org Subject: Re: svn commit: r357767 - head/net/cyphesis Message-ID: <CAF6rxg=wzLZ9TOcw69LTzw_9A%2BY1LmryGUQQutYoHRGFu2gzxA@mail.gmail.com> In-Reply-To: <20140623110419.GA81323@FreeBSD.org> References: <201406141111.s5EBBCgV016094@svn.freebsd.org> <539C8682.3030603@marino.st> <20140614202139.Horde.HZsy3djMLtU53sefqx-bAg8@avocado.salatschuessel.net> <539C94C3.4040606@marino.st> <20140623110419.GA81323@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 23 June 2014 04:04, Alexey Dokuchaev <danfe@freebsd.org> wrote: > On Sat, Jun 14, 2014 at 08:30:27PM +0200, John Marino wrote: >> P.S. why not ask a c++ guy for help? As a non-C++ guy, the error seems >> relatively simple (header/namespace related). Is it really hard to fix? > > Big +1. I'm really frustrated to see lots of us trying to figure our how > to workaround C++ related build failures via some USE_GCC or USES=compiler > magic instead of actually look at the code and try to fix it properly, so > it builds with *any* supported compiler. While it is nice to do this, it is not something that we should expect all maintainers to do. The minimum bar here is "ensuring the port works with upstream's (un?)documented requirements". -- Eitan Adler Source, Ports, Doc committer Bugmeister, Ports Security teams
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxg=wzLZ9TOcw69LTzw_9A%2BY1LmryGUQQutYoHRGFu2gzxA>