Date: Sat, 27 Aug 2011 12:38:57 +0400 From: arrowdodger <6yearold@gmail.com> To: Igor Soumenkov <2igosha@gmail.com> Cc: freebsd-ports@freebsd.org Subject: Re: How to escalate? ports/159276 - cmake Message-ID: <CALH631kYZ9W6EPWvfVAZs6ks3-oQXMwC%2BJ2tymZ4ACD=JDjZ8A@mail.gmail.com> In-Reply-To: <4E58A6AA.4060805@soumenkov.com> References: <4E58A6AA.4060805@soumenkov.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Aug 27, 2011 at 12:11 PM, Igor Soumenkov <2igosha@gmail.com> 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? > > -- > Igor Soumenkov > > 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. > > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > I'm suffering from this problem too.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALH631kYZ9W6EPWvfVAZs6ks3-oQXMwC%2BJ2tymZ4ACD=JDjZ8A>