Date: Tue, 23 Aug 2011 12:25:15 +0400 From: igor <igor@soumenkov.com> To: <freebsd-ports-bugs@freebsd.org> Cc: Max Brazhnikov <makc@freebsd.org> Subject: How to escalate? ports/159276 Message-ID: <ba84f7cad21bdcb036b547d5a5e8bc58@soumenkov.com> In-Reply-To: <b1e7101b853962f0ac0adc1987f99634@soumenkov.com> References: <201108221124.p7MBO4p1018433@freefall.freebsd.org> <f768914fbb985b3e920c6331c38f1f11@soumenkov.com> <201108221318.02398.makc@freebsd.org> <b1e7101b853962f0ac0adc1987f99634@soumenkov.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Dear all, How can I escalate the issue related to one of the ports? It seems that the comitter who introduced the problem with a patch (http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/cmake/files/patch-Modules_Compiler_GNU.cmake?rev=1.1) to the port does not want to do anything with it. There is a PR open (159276). Cmake is widely used in the company I am working for, and now as a FreeBSD user I get cmake that is different from everyone else's, because my default Debug and Release build have empty CFLAGS. Now I have to manually fix these flags back each time I reconfigure my build directories. On Mon, 22 Aug 2011 17:38:44 +0400, igor wrote: >> It a usual practice to close duplicated reports. The patch in >> question was >> added for some reasons and we can't just remove it, until we find >> better >> solution. > > The patch altered the way original cmake behaves. It all worked very > well until someone added this patch. It works well in Debian, for > example. > This makes it very inconvenient to use cmake from ports for software > development. -- Igor Soumenkov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ba84f7cad21bdcb036b547d5a5e8bc58>