[SOLVED] Best practice for installing Slackware 14 without X
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Best practice for installing Slackware 14 without X
Hi everyone. Normally when I set up a Slackware server, I include everything in the "kde", "x", and "xap" package groups, and also setup everything in the "l" package group to avoid dependency problems. This time, I'm setting up a new Slackware server that doesn't require X, so I didn't include the "kde", "x", and "xap" groups, but still installed everything in the "l" group. Now I am getting missing dependency errors at startup when rc.M calls /usr/bin/update-gtk-immodules, /usr/bin/update-gdk-pixbuf-loaders, and /usr/bin/update-pango-querymodules, looking for libraries included in the "x" package group. Not needing any of these packages, I removed them with slackpkg, which got rid of the startup errors, but then realized that there are other X specific packages in the "l" package group that are not needed if X is not installed, such as Qt.
Just wondering what everyone else does when they install a system that doesn't need X? Am I better off only installing actual needed libraries from the "l" group?
Do note that even though your server itself might not have a proper screen, you might need X-libraries to install certain products. I know for a fact that Sybase needs to be installed (remotely) via a GUI program. I'm almost certain that Oracle does too. In the end, trying to exclude certain packages "just because it's a server" will likely be counterproductive.