Docsonic wrote:
Firstly, I would have to compile at work so it would definately not be a daily thing, probably not even weekly - irregular at best.
I haven't been very regular at building packages lately. But perhaps if there were two of us working together we could do a better job. I bet life would be much better if we built the official release packages on an older system like etch too.
Secondly (and probably more importantly) I am going to have to sort out the GTK problems first. I am fully up-to-date on the 'Etch' packages and my GTK setup is too old. This means that every other Etch user out there has the same problem. I understand the reasons for going for unstable or testing to get the up-to-date libraries but, unfortunately, the machine in question is our mailserver and I am not willing to go off stable for that. Having said that, I will see what backports are available for GTK and if need be, look into compiling from sources.
Actually I think the GTK thing may need to be resolved on the Inkscape end. If we haven't moved as a project to start using 2.10 then this is an important bug to fix. I just don't remember what our plan was. I'd have to go digging through the list archives to find the final word.
Aaron Spike