On Wed, Sep 29, 2010 at 18:16, Ken Moffat <[email protected]> wrote:
> On Wed, Sep 29, 2010 at 12:03:41AM -0500, DJ Lucas wrote:
>> While I'm not personally a fan of KDE/QT, it seems to me that a lot of
>> people here are (or at least were until KDE4)
>
> [rant]
>
>  Ah, there's the rub - kde3 had poor font handling, but was
> straightforward to build and had some nice programs.  Kde4 had much
> better font handling the last time I looked (4.2, I think), but
> ever-increasing dependencies and the obnoxious cmake[1] : For us,
> it's just a replacement for ./configure, but it comes with its own
> baggage and is generally incomprehensible for anyone used to building
> 'nix software.
>
>  It also is *not* targetted at people who build from source using
> released tarballs.  When I was trying to build it, I used to rely on
> other distros to package particular svn versions of some of the
> prerequisites as tarballs.
>
>  It's also *over-large* (I can think of other words to describe its
> size, but they are offensive).
>
> [/rant]

+1

>
>  However, kde3 can't go on for ever - ISTR there was a report of
> someone maintaining the last version, but I've seen nothing since
> then.  If people *want* to use current kde4, and have enough CPU and
> disk space to build it, *please* speak up.  One of the ongoing
> problems with BLFS is that it already contains too many packages
> that no editor seems to care about.

oh, you mean KDE Trinity?
I've gotten in contact with Timothy Pearson, he's releasing 3.5.12 soon.
When that happens, I can put a stable 3.5.12 into the wiki.

(But right now, I'm much to busy. and 3.5.12 isn't ready yet)

>
> 1. I call cmake obnoxious for two reasons - the less-important is
> that it reinvents the wheel for us, the more important is that it
> appeared to enforce static libs as well as shared (can you say
> vulnerability?).

ew, cmake. I wish that KDE never used it.


-- 
later, Robert Xu
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to