Splitting gtk stuff into a separate package
Eugene Kirpichov
I think it's worth cutting gtk-related stuff (all that depends on -fgtk) into a separate package for the following reasons:
* building gtk bindings is horrendously slow, up to an hour or two with profiling, and it gets repeated if you mess something up (happened to me more than once). It's very good to eliminate this from a clean install of Chart.
* on some platforms (eg the default amazon ec2 Ubuntu image) gtk carries a ton of dependencies which are also sometimes difficult to install and easy to mess up (I messed up my ec2 env so much that I surrendered)
* usage of Chart without -fgtk is very common, so it's a completely orthogonal part and can be safely split out.
I have actually completed the split on my machine, but I'll be able to send the patch only tomorrow.
In the meantime, please let me know what you think:
* is this a good idea?
* if yes, how would you like to name the gtk package? Is Chart-gtk fine?
* do we need a new darcs repo for that package?