It doesn't work because the abicollab plugin needs to be built with an special flag so Sugar support gets compiled in. Have tested that adding the flag as follows makes it work: -CXXFLAGS="-L$RPM_BUILD_DIR/%{name}-%{version}/src/wp/main/unix/" %configure --disable-gda --enable-libabiword --with-abiword=$RPM_BUILD_DIR/%{name}-%{version} +CXXFLAGS="-L$RPM_BUILD_DIR/%{name}-%{version}/src/wp/main/unix/" %configure --disable-gda --enable-libabiword --with-abiword=$RPM_BUILD_DIR/%{name}-%{version} --with-abicollab-sugar-backend
Oh - I checked the spec for that but did overlook that there was a %if %{olpc_build} switch. I guess we do not build olpc only packages anymore - so I guess we can take that switch out.
The OLPC switch is still needed, since it enables a few explicit OLPC specific patches. Building the sugar backend unconditionally is probably not a good idea yet, as it enables (using DEFINEs) some rather b0rked code for normal systems.
I wonder how we can move on with that then. Would be pity if Sugar on Fedora would not have the collab ability. And as OLPC can not carry any forked packages anymore - there has to be another solution. Of course you as a maintainer know best the abiword inner parts to comment on those best.
Marc, is there a realistic time frame about how much time it would take to enable sugar support without hurting other users? Is this doable for F11, or a more long term project?
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Quite a bit of work has gone to AbiCollab during the 2.8 version of Abiword. Marc, has this issue been addressed or do we stand in the same place as before? Thanks!
I *may* have fixed it, but i may also have broken it... I can see 1 crasher happening, but that would not happen in the sugar environment, but in the normal environment. Try it I'd say (I think I enabled the sugar backend in F12)
It seems the collab isn't enabled in the standard build in rawhide atm. I did notice a fix in collab in the 2.7.8 release but I'm not sure if that's the fix your referring to. Also what's the difference between the collab-backend-sugar or the "normal" backend? %if %{olpc_build} %configure --disable-static --enable-dynamic --disable-gnomevfs --disable-gucharmap --disable-printing --enable-plugins="loadbindings collab" --enable-collab-backend-sugar %else %configure --disable-static --enable-dynamic --enable-plugins --enable-clipart --enable-templates %endif Of the above differences (other than the collab) I think gnomevfs and printing are no longer valid now abiword uses gtk/gio/gtkprint, not sure how much size gucharmap brings to the table, and if the clipart is large it probably should be in a noarch subpackage anyway. The only other difference in the olpc build I can see is the following patches: %if %{olpc_build} Patch100: abiword-2.6.4-defaultfont.patch Patch101: abiword-2.6.4-draghandles.patch Patch102: abiword-2.6.4-nohtmloptions.patch %endif Not sure if they're still valid if the build is working OK on sugar currently (minus collab of course).
Has anybody tested this lately? Is this still an issue? Would be good to know for the upcoming SoaS release.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Is this now fixed?
Tomeu can you confirm if this is still and issue?
(In reply to comment #12) > Tomeu can you confirm if this is still and issue? Yes, this is confirmed to work in F12-based Blueberry. Thanks all for your help, specially Marc.