I admit it's a little disappointing that we are a full 4 years out from the last release and still no 15.0 beta on the horizon or even Plasma 5 in -current. I'm happy to continue running -current with Plasma 5 from ktown, but I wonder what the holdup is.

1 members found this post helpful.

That said, this endless debate about dependency resolution and minimal installs is like beating a dead horse. If you want to skip some large sets of packages, it's easy enough to do that without causing any problems. If you want a true minimal install, either figure it out yourself and deal with the dependency issues, or use a different distro. That's one use case Slackware isn't designed for, nor will it probably ever be. Complaining about it is a waste of time.

3 members found this post helpful.

You're cracking me up.

But that may be because I read every post you make in the voice of a character from a certain Canadian sitcom:

https://www.youtube.com/watch?v=Trpr_cV3hJ8

3 members found this post helpful.

Actually, it's not a requirement. It's a recommendation.

I've got servers running nothing more than the A, AP and N series. Even with less than 2.5Gb of software installed, they have all the services I need. Those boxes will never be used to compile anything and run headless. As per Mr. Spaier's experience, they run like Swiss watches. You can set 'em and forget 'em. They'll hum along doing their job/s quietly and reliably. Either VM or physical.

The full install is often recommended for newbies because it helps with troubleshooting. Outside of that, you can do whatever you want. There is no "requirement" for anything. Slackware doesn't stop you from removing package X because package Y depends upon it.

So you can easily break it... But my experience is that there is no better way to learn! Pull it apart. Put it back together. Break it. Fix it. With Slackware you have the power.

9 members found this post helpful.

In the middle of 90s full install was appropriate method. Today doing this is completely stupid installation step. One more thing to blame the setup program: it's not just obsolete and degraded, but it also misleads users with this old recommendation.

The next person who posts in this topic volunteers themselves into creating a Slackbuild for QMPlay2-20.07.04 and getting it to build for me. It uses cmake, clang, and ninja.

1 members found this post helpful.

Nothing in this quote is correct. Begone, energy vampire.

3 members found this post helpful.

Since the post is at the same time as mine I'll let Geist slide

1 members found this post helpful.

I'm half tempted to do it, though. Just to get more experience with ninja/meson whatever.
That said, it's probably not going to be a quick thing.

1 members found this post helpful.

I created a SlackBuild and will build a package after I finish with other work. You'll find it in my repo soon.

10 members found this post helpful.

You can't prove otherwise. Btw, go and prepare QMplay2 SB :-) You are assigned to volunteer for that.

1 members found this post helpful.

You are like Donald Trump. You contribute nothing for the greater good and only strive to antagonize people which you need to boost your own ego. You are a sorry little man. Go back hiding under your rock.

9 members found this post helpful.

Continuing your comparisons, you are more like Nancy Pelosy or Alexandria Ocasio-Cortez. You make naive statements without prior verification and simplistically divide the world into black and white ignoring complexities.

1 members found this post helpful.

Instead of watching sitcoms, tell us better if -current Slackware users should start using pkgsrc (in replacement of SBo) in order to have more or less recent software.

instead of keep assigning work to others (remember that we don't work for you), why don't you tell us?
use it for a while with current and then report to us your experience.

4 members found this post helpful.