> > Should package builders have the option to disable many of these > resources? Yes, they should have the option. Possibly Trinity can be > delivered in two flavors. One is with all hooks enabled. The other with > most disabled. Users of older hardware and those who don't need bling can > download the latter set of packages. Just a thought. Great idea! Shouldn't be too difficult either; two separate repositories built from the same source, but with different configure options, should do the trick. > > I hope I haven't overstayed my welcome! > Not at all! The Trinity project should be learning from KDE4's mistakes, not repeating them. ;-) In fact, when I go into kdepim to fix your build failure, I will add flags to disable each resource independently. Then I'll leave it up to you to disable any resources that Slackware users won't be interested in. Tim