On Mon, 19 Jan 2009 08:26:55 +1000, Dima Panov wrote:
> BTW, kdebindings will require ruby19 instead of ruby18. With ruby18 module
> RubyQt is unbuildable at current state.
It's not a big problem, different ruby versions can coexist.
Just define ruby required version:
USE_RUBY=yes
RUBY_VER=1.9
> For mono/c# - mono20 is required. Google/bsd-sharp-tree is suitable for
> this dependency, 'cause ports have only mono10.
The work is going on mono-2.x ports, though unlikely they will be committed
before KDE-4.2.0 release.
> I'll try to settle kdebindings into ${LOCALBASE} and play with RubyQt as
> soon as my test laptop will return from service lab.
Ok.
Just to mention, the problem is not to install kdebindings into ${LOCALBASE}
(it can be done, I'm sure), but to assure that Ruby/PyKDE dependent ports will
build/work fine. But this is next step.
Greetings,
Max
_______________________________________________
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information
