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.
Distribution: Slackware 13.37 (64-bit on desktop, 32-bit on netbook)
Posts: 17
Rep:
Only 16 packages for me.
This is for my 13.37 desktop. I pretty much have things how I want them at this point. But I would be interested in seeing the full list and how popular each package is. Might find a gem or two I didn't know about.
I just ran all the submissions through the processor and here's how it stands at the moment:
Code:
=== Machines ===
total: 125
32-bit: 68
64-bit: 57
=== Packages ===
Total number of unique packages: 1709
Total number of package installs: 9306
Average number of packages per machine: 74
Moving to the top packages by number of installs, there's a nice three-way tie at the top between lame, libsigc++ and unrar. I'm a little surprised that two of the four most popular packages are compression (well, uncompression) utilities. Less surprising is the number of codecs in the top 20.
I noticed a few other things. A lot of people are clearly customising their SlackBuilds to use a newer version than the 'official' script (see calibre for example). A few people have added the _SBo tag to non SBo scripts (what's extra.fonts?). And someone out there has installed DevIL without a version number (DevIL--x86_64-3).
101, though I should really pare that down a little. I suppose it evens out, though, since there are one or two that have my own $TAG because I changed the SlackBuild too much.
Whoops, never mind, I left the SBo $TAG on the main one I was thinking of (Mixxx). In any case, Sauerbraten is about to be uninstalled, and I am about to decide that Wesnoth is taking too much of my time to stay. And NetworkManager needs to go, too. Maybe someday I'll prefer it over Wicd, but not yet.
Submitted my 6 :-)
Have the tendency to build my own slackbuild scripts from my own template; I hate it that SBo puts everything in /tmp; clobbers that dir up too much for my taste... I like to have /tmp as clean as possible.
@Ramurd - on traditional Unix boxes (eg Solaris, AT&T SVR4, etc) /tmp does not survive a reboot. Thus after a clean boot, /tmp is empty. I've always wondered why Linux has never done this. Easy to remedy of course - merely add a few lines of 'rm /tmp/*' and
'rm /tmp/.*' to one of the early startup scripts.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.