Linked by Eugenia Loli on Sat 15th Jan 2005 02:09 UTC, submitted by Paul Best
Slackware, Slax On a recent IRC discussion Pat discussed Slackware's future and the restructuring that will happen for Slackware 11. Regarding the removal of Gnome from Slackware, he said: "GNOME is not easy to build into packages, lacks decent documentation to build, and requires many undocumented system changes for things to work 100%".
Permalink for comment
To read all comments associated with this story, please click here.
Re: to Eugenia and Morgan
by Best on Sat 15th Jan 2005 04:43 UTC

Our reason for including our own gtk and x packages is one largely of performance and installation concerns. On our lowest end machines especially, the optimized X server performs better than Slackware's own. It also allows us to keep certain packages up to date as Gnome requires them. Lets face it, before now, if Dropline didn't replace Slackware default packages, it wouldn't exist at all.

Many of our users also install onto a Slack installed without the duplicate files. This allows people to do a 2 CD install, instead of a 3 CD install (this probably won't be an issue from this point on). In the case of PAM and the various packages related to it, the primary issue is one of desktop usability. PAM support does seem to be the big difference between Dropline and Slackware.

Most of the differences between a stock Slackware and Dropline are to allow us to get Slackware to do the same kinds of things you get out of more Gnome desktop-centric distributions, Howl/Rendevous support, Hal/Dbus, GUI configuration tools, etc.

If anyone does know of any current Slackware/Dropline compatability problems, or crash bugs, I'd love to know about them. We do tend to be quite bleeding edge if you keep up with all the updates. This is something we're working on.