SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
What packages are needed for a minimal/base KDE 4.10 install?
I want to create a punch list (things to do) for updating my HTPC to KDE 4.10. As I'm new to KDE4 I'm uncertain which packages constitute a minimal/base install. The HTPC does not need the whole suite of packages.
I mostly use Xbmc but I still need a desktop. I need a desktop environment that easily supports user restrictions, such as KDE. I need basic file management for performing occasional maintenance.
What do you mean by "user restrictions"? Depending on the login manager, the typical user can choose his own WM if he doesn't like KDE. Normally the restrictions are set when you add a new user.
What packages are needed for a minimal/base KDE 4.10 install?
I want to create a punch list (things to do) for updating my HTPC to KDE 4.10. As I'm new to KDE4 I'm uncertain which packages constitute a minimal/base install. The HTPC does not need the whole suite of packages.
I mostly use Xbmc but I still need a desktop. I need a desktop environment that easily supports user restrictions, such as KDE. I need basic file management for performing occasional maintenance.
Thanks again!
With Slackware, it's not exactly easy to go for minimal installs, as you can do with Debian or CentOS. One possibility though: take a peek at Slax' sources to get some inspiration. The Slax 7.0.x series is a very clean implementation of what a minimal KDE 7.9.5 desktop can be.
kde-baseapps
kde-runtime
kde-workspace
kdelibs
konsole (maintenance app)
kate (maintenance app)
Possibly these:
kde-wallpapers
kde-base-artwork
I don't see any need for activities or nepomuk on the HTPC. I was hoping I could build only one package set for both my office system (full package set) and the HTPC, but looks like the build script build order includes nepomuk-core early in the process. I probably have to include that to avoid building separate package sets. The build script rebuilds a few packages, so this could be a mess trying to avoid building separate package sets. Oh well.
kde-baseapps
kde-runtime
kde-workspace
kdelibs
konsole (maintenance app)
kate (maintenance app)
Possibly these:
kde-wallpapers
kde-base-artwork
I don't see any need for activities or nepomuk on the HTPC. I was hoping I could build only one package set for both my office system (full package set) and the HTPC, but looks like the build script build order includes nepomuk-core early in the process. I probably have to include that to avoid building separate package sets. The build script rebuilds a few packages, so this could be a mess trying to avoid building separate package sets. Oh well.
If you wont add widgets to panel or desktop you need kdeplasma-addons and kdepimlibs
For a minimal install, you can also go for Salix/KDE (respectively add slapt-get on top of a base Slackware install). Install the base KDE packages as suggested above, but use kde-baseapps-lite instead of kde-baseapps. Then, add what you need with slapt-get. What you get is a lightweight KDE desktop with just a minimal set of applications. Tested it here, works great.
If you wont add widgets to panel or desktop you need kdeplasma-addons and kdepimlibs
Thanks. A lot of this I probably would figure out by trial and error and that might still be the final approach, but I started this thread to at least find a starting point. I do get a kick from using the moon phase widget and have had that enabled on my HTPC since the days of KDE3. So looks like I'd need those packages too.
Quote:
For a minimal install, you can also go for Salix/KDE (respectively add slapt-get on top of a base Slackware install).
Thanks, I appreciate that. Yet one of my goals is to minimize my maintenance. I'm growing old and cranky with respect to excessive fussing with computers. I've been using desktop computers for more than 30 years and while tinkering remains fun, seems as I age I want to maintain them less each passing year.
I'm using Slackware 14.0, which has no official updates for KDE. Mixing and matching package sets is more work and there is no guarantee the maintainer of any package set will keep the point releases up to date. Eric created a KDE 4.10.1 package set but he might not continue doing that with subsequent point releases, which would be understandable. I prefer to update the point releases because they are bug fix releases. Therefore I have to build my own package set, which mostly I don't mind, but I'd rather build one package set for myself and then install the minimal necessary packages on the HTPC.
Many KDE packages are not needed for my HTPC, such as PIM apps, development apps, etc. Other than the base apps such as a file manager and kate/kwrite, I use amarok, kaffeine for quick TV capture card testing, and k3b. Xbmc is used most often.
I realize there remains among some users much hate and discontent for the evil triplet, but seems they behave well nowadays with 4.10.x. On my office system I have nepomuk disabled right now, but I see possibilities for that kind of back end --- some day. Likewise for activities. I understand their purpose but right now my computer needs are uncomplicated and I have no use case for them. Nonetheless, I have changed my mind about learning how to build a KDE Lite and although the HTPC would have no need for nepomuk or activities, or strigi or akonadi, I am not inclined at this time to spend time building or maintaining a separate package set. Seems easier to instead create a skeleton profile with all of that disabled.
Yeah, everything is perspective. Well, I use Slackware. Have been for 10 years. Building packages is more or less status quo. I admit sometimes I grow tired of building packages and think about a different distro where I just point-and-click to download packages. Then I think about dependency bloat and decide that building packages probably is less painful. Especially when I want to keep using an older version of a package because the newer versions are not designed the same. (Did I just say XBMC?) To me then, reducing maintenance is building one set of packages for all of my systems. I admit doing that is getting more challenging with the old hardware around here, which is one reason I have stayed with 32-bit for everything. Lazy.
I probably should retire the old stuff. I don't do much with them any more. Although I'm a wee bit amazed I have Slackware 14 running on them. Perhaps Slitaz or Puppy would be better suited for them, but I have neither the time nor interest to distro hop or mix distros. Lazy.
Twenty years ago I laughed when I watched the movie Grumpy Old Men. Now I am one and grumpy old men are lazy.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.