On Monday, March 23, 2015 04:21:31 PM Dinar Valeev wrote:
So, IIUC
We want to build bindings with Mono by default for KDE to be prepared to the fact some user will come and build 'third party' against libkolabxml. And we want to be prepared for that.
No, it is not if we want to prepared for this or that. The main discussion point is if we accept to drop certain functionality or not. If we want to deliver a complete KDE experience, then we need to deliver the mono bindings as well. It is not only libkolabxml, but also packages likes mono-kde4 and mono-qt4, which delivers mono bindings for KDE and Qt.
for GNOME we want this for banshee and tomboy?
I believe that Dominique clearly indicated that both Banshee and Tomboy would require mono in order to be build at all. So this would mean that if we drop mono, we would also drop banshee and tomboy. And I wonder what is the reasoning behind this ? Does it really take so much work in order to maintain mono for openSUSE ?? Or is the fact that it doesn't build for other arch's, the reason to loose functionality on the main i586/ x86_64 architectures ? Don't tell me that this is to save buildcycles or something like this, because packages needs to be build anyway. Whether with or without mono. Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org