Inkboard enables collaberative work over XMMP/jabber. This requires --enable-inkboard AND >=net-libs/loudmouth-0.17.2-r2. Personally, I'd require >=net-libs/loudmouth-1.0.1 and release an -r1 on the ebuild when the other goes stable, with the new USE flag.
Created attachment 73439 [details] 0.43 ebuild with 'inkboard' USE and without 'bonobo' USE I'm pretty sure the bonobo USE flag doesn't affect inkscape's configure any more. And I've added the 'inkboard' USE flag with a dep on net-lib/loudmouth. I guess this should be 0.43-r1?
i think some --with are not taken into account, like : --with-xft use xft scalable font database (default is auto) i dont see the bonobo enable anymare, like jesse said. There is nothing about it into the configure. and maybe something has to be done for : --with-gnome-vfs use gnome vfs for loading files (or not, i dont really know the link with the other uses available :)
(In reply to comment #2) > i think some --with are not taken into account, like : > --with-xft use xft scalable font database (default is auto) > > i dont see the bonobo enable anymare, like jesse said. There is nothing about it > into the configure. > > and maybe something has to be done for : > --with-gnome-vfs use gnome vfs for loading files (or not, i dont really > know the link with the other uses available :) Unless someone is willing to add these features quickly, is there a problem releasing an -r1 ebuild with the inkboard USE flag as present in the 2005-11-23 attachment?
added jabber support in -r1, sorry for the delay, ppc64 team please mark it ~ppc64 once loudmouth is ~ppc64 I'll have a look about gnome-vfs later (the bug remains open for a day as reminder)
thanks for info. readded ~ppc64.
> Unless someone is willing to add these features quickly, is there a problem > releasing an -r1 ebuild with the inkboard USE flag as present in the 2005-11-23 > attachment? I don't understand it... it's 2007-02-02 and there's still no such use flag (!) and jabber support is *not* there - using version 0.44.1 from portage.
In case someone else finds this bug in future, take also a look at bug 162620, which is very similar to this one.