So far Qt4 from area51 ports seems fine. Pending some decisions on final port naming/splitup/etc, I would say it's ready to go. Going down the list of notes on the wiki:
* I don't think the qtdemo port should be the master port to pull everything in with. Qt4 should fill that roll. Perhaps it can have an option to pull in qtdemo. * qtdemo is working well for me. See my earlier email on not building webkit or phonon examples. Building the examples by hand, browser and mediaplayer are working as expected. * designer didn't segfault on me, though I think I might have caught it rebuilding some built libraries. I would have to rebuild to verify. * qdbusviewer correctly showing system and session channels. * Regarding qtconcurrent tools, I didn't even know they existing until I saw this mention of them. They are not referenced in tools.pro, so I would assume they're safe to ignore. * Regarding translations. You could make them a separate port, but it might more sense to install the appropriate translation sets with the various parts of Qt (qt_xx with core, assistant_xx with assistant, etc). Finally, some notes on some other stuff I have built: * Strigiclient is indexing and akode is playing music. * We need a QCA2 port. trunk/kdesupport says "Please install the qca2.0.0 package from your distribution or build from source if you want to use qca with KDE trunk." * Soprano and qimageblitz built, but unable to test at this time. p.s. This is all on 7.0-RELEASE, with no KDE3 around. -- David Johnson _______________________________________________ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
