[kde-freebsd] ports/116484: [PATCH] OPTIONS'ify x11/kdelibs3

[Doug Barton]

The following reply was made to PR ports/116484; it has been noted by GNATS.

From: Doug Barton <dougb at FreeBSD.org>
To: Michael Nottebrock <lofi at freebsd.org>
Cc: bug-followup at freebsd.org
Subject: Re: ports/116484: [PATCH] OPTIONS'ify x11/kdelibs3
Date: Fri, 21 Sep 2007 11:53:10 -0700 (PDT)

 On Fri, 21 Sep 2007, Michael Nottebrock wrote:
 
 > The libthai dependency will not be made optional, since it is not a
 >>> localization feature - it is required by khtml's text rendering engine.
 >>
 >> Well that's just silly of them. Is it possible to make it optional there?
 > When it's turned off, khtml will still work, but it will not display
 > Thai correctly.
 
 My point is not so much that libthai is an overwhelming burden, but more 
 so that only a very small percentage of the user base will ever need it, 
 therefore I don't see the point in enabling it by default.
 
 If it can be optional, I think it should be, FWIW.
 
 > It's somewhat beside the point, but I am continually surprised about the
 > fact that nobody has ever asked for image format support libraries to be
 > made optional in the KDE ports instead - for a couple of them, the much
 > more convincing argument of increased security by avoiding code with a
 > bad security history could be made ...
 
 Personally I think a lot of stuff should be optional in the KDE ports, 
 including these libraries, but since the kerberos issue actually breaks 
 the build for me I started with this one. :)
 
 That said, given that KDE 4 is right around the corner, it would perhaps 
 be more useful to look at a new framework for it, including OPTIONS 
 wherever practical, especially in the metaport. I would be willing to 
 assist with this effort.
 
 >>> The kdelibs3 Makefile does not contain an explicit dependency on
 >>> kerberos. The configure check should simply fail to detect kerberos and
 >>> then configure kdelibs to disable support for it. Does the configure
 >>> script fail for your if no kerberos is installed on the system?
 >>
 >> The configure script does not fail, the build fails. I agree that it
 >> is a condition that should be detected automatically, but it
 >> definitely isn't.
 > Interesting - can you supply a log of such a failed build, including
 > config.log and the output of ls /var/db/pkg?
 
 Yes, I can do that, at worst by the end of the weekend.
 
 Doug
 
 -- 
 
      This .signature sanitized for your protection