How to escalate? ports/159276 - cmake

Sam Cassiba sam at
Sat Aug 27 14:17:38 UTC 2011

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
>>> (
>>> 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. 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 at>

More information about the freebsd-ports mailing list