And break Slack 11 compatibility... the gtk package that comes with vl 5.8 is the default one from Slack 11. So if gtk 2.2.8 packages don't work properly on 2.2.10 it would be a release for which linuxpackages.net and slacky.eu are no longer useful package resources (at least for apps that use gtk).
But the GTK upgrade doesn't break GTK 2.8-based packages, Xfce and the rest continue to work after the upgrade (except for wifi-radar).
Anyway, I wouldn't have uploaded the packages if they were "destructive", its one of the reasons it took me so long to get GTK and GNOME finished: test packages, fix problems, test again, fix other problems, test again, fix, fix, fix, test, test, test, and so forth untill it worked...
But yes, I do agree with sticking to "major" Slackware packages for official releases of VL.
So we have a few options, based on the discussion in the thread (but not limited to):
-nuke the packages
-create an "updates" repo
-create a gnome repo, where everything that gnome relies on, upgrade-wise, must be moved to along with the gnome core packages
-create a new release of VL with these packages as a base
Now its really up to the VL elders to make a decision regarding this