Date: Sat, 27 Aug 2011 09:17:36 -0500 From: Sam Cassiba <sam@cassiba.com> To: Igor Soumenkov <2igosha@gmail.com> Cc: freebsd-ports@FreeBSD.org Subject: Re: How to escalate? ports/159276 - cmake Message-ID: <4E58FC80.9060405@cassiba.com> In-Reply-To: <4E58F3B4.8060706@soumenkov.com> References: <4E58A6AA.4060805@soumenkov.com> <4E58F04F.7030008@cassiba.com> <4E58F3B4.8060706@soumenkov.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08/27/11 08:40, Igor Soumenkov wrote: > > On 27.08.2011 17:25, Sam Cassiba wrote: >> On 08/27/11 03:11, Igor Soumenkov wrote: >>> Dear all, >>> >>> How can I escalate the issue related to one of the ports? >>> Cmake in ports sets different cflags than the original one. It seems >>> that the comitter who introduced this 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. >>> >>> If nobody cares about this, why not place a big 'we don't care about >>> developers' banner on the main site? >>> >> >> devel/cmake is maintained by the kde@ team, so my recommendation would >> be to ping them directly. http://wiki.freebsd.org/KDE4 should have the >> droids you seek. >> > Unfortunately, one of them ( Max Brazhnikov (makc@) ) is the committer I > am writing about. > And I CC:ed the kde@ mailing list, but got reply only from Max. I quoted > it here ("we can't just remove it...") - he is not going to fix it, and > he is not replying to my e-mails anymore. > That is why I am trying to find someone who can help with this situation. After looking at the patch, it would seem that you would need to set your CFLAGS in /etc/make.conf to do what it (the patch) removed. Other than that, maintaining your own local port of cmake would be an alternative to investigate. -- Sam Cassiba <sam@cassiba.com>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E58FC80.9060405>