8:19:01Colleenloke: oleo said 11 hours, 12 minutes ago: tell me how far you got with the mcclim-freetype2 backend, i obviously get many errors and am also in the process of checking the old mcclim sources of it to see what has changed since then, i'm not sure i could see errors right away especially if they are ffi/cffi specific, old code also seems to have had a different facility like alien or so for a more generic ffi than just cffi i think
8:19:21lokeoleo: I've used my branch exclusively for a while now and for the most part it works very well.
8:23:12oleoloke: i get an error with http://dpaste.com/22F1R3C as http://dpaste.com/1QRCND6
8:24:02oleoloke: i'm dumping an image, and so far the image gets dumped but when trying to start the image i get that error there, and additionally cl-freetype2 fails it's tests too
8:41:07lokeI saw you had some other errors with missing symbols, and that's also because of your harfbuzz lib version
8:41:27loke(like I mentioned, I don't actually use those, so for CLIM I could disbale that to make it work on older versions)
8:49:54oleono idea who decides to use which version of harfbuzz when it comes to distros, it's not obvious from the version spec of the distro package manager which version it corresponds to actually
8:56:57oleowait a little, does that also mean all the other libs i depend on are old too ?
8:57:51lokeoleo: Probably, but for the most part you wouldn't notice since I don't really use any of the new features.
8:58:30lokeFor harfbuzz, however, I've added support for a bunch of functions that I don't actually call (the functions that are listed in the header files of the version I was using when developing the CFFI wrapper)
8:58:56lokeThat might not have been the best idea for CLIM, but I didn't realise that there were so many new functions.
12:36:27oleook i installed all the required libs manually