I'm using Yum, Zypper and RPM on a daily basis, and frankly, it's a no-brainer. Of course it always depends on the distribution you're using and the way the dependency information is implemented in the packages, but as far as I remember, the last time I had to think hard to resolve dependencies was back in 2010 when I installed an Oracle Linux server for the french motorway company on a closed circuit without Internet access and no local package repository.

On a side note, if I had the means to build my "perfect" Linux distribution from scratch, it would closely resemble Kongoni Linux, a Slackware spinoff with KDE as main desktop and a ports-like system to manage software. Unfortunately the Kongoni guys went down the 100% Libre path, so the system was effectively unusable on most modern hardware.

Well, it's either that or after hanging around here so long you've worked around all the problems?

2 members found this post helpful.

slackware.com is dated, maybe a link to this thread on slackware.com could help people interested in slackware?

2 members found this post helpful.

Dated how? Do you base that just on appearance? I ask this because I know many do. They see the simple B&W text format and assume it's old. They simply mistake form following efficient function for old. Why do so many require glitz and glamour that only serves as eye candy bloat for a page you will visit only rarely? When I, and I assume most Slackers, go there it is to get something quickly and get back to work or play asap. Simple is fast and efficient. Glitz is slow and often confusing. I think Slackware.com is perfect as it is. No matter how pretty the wrapping paper, ribbons, and bows are, if the gift inside the packaging is a turd, it's still a piece of shit.

2 members found this post helpful.

I think you misunderstand the issue that has been raised. It is LITERALLY dated. As in the dates listed on each news post. These questions are prompted by the actual datestamps listed on the homepage. Think about it from the perspective of someone who has no prior knowledge of Slackware.

The last "update" from the "slackware team" is from 2016. The one before that was 2013. And then another from 2013. This is the type of fading activity that generally indicates that the project is dying, or unmaintained. In the case of Slackware, this is not correct. The problem itself is really simple - a website is considered the "face" of a project, which present one of the 3 following states:

1) Project is new
2) Project is old
3) Project is discontinued/abandoned

People are browsing to slackware.com and choosing option #3. The activity on slackware's homepage does not accurately represent the activity of the project or community. I find it unfortunate that we would promote the ideal of simplicity to such an extreme that we fail to provide accurate information regarding the current status of the distro.

My understanding is that 2016 was the last stable release of slackware (14.2). A lot has changed since then. A huge amount of development has taken place in -current. SBo became an official source of build scripts, and one of the core team members puts a lot of effort into making sure ktown compiles and runs as a really slick and modern desktop. These are all things that added to the quality of slackware, but nobody knows that they happened. It's buried in the depths of this forum.

To this day I'm still not entirely sure where the official link to donate is. And I've been using Slackware for over 15 years!

8 members found this post helpful.

I can't find the post but I believe PV had commented at one point that the website is kind of broken and he isn't sure how to fix it, and that posting 'news' is really just him hand modifying a file. So unless my memory fails me and I'm making this up, then yeah I'd say it's pretty dated. I personally agree with not wanting some crazy bloated stupid website.

Excited to see the progress, sounds like -current is about to get really busy.

1 members found this post helpful.

From the website...
Text is also in the readme files...

As suggested before, Pat could use a secretary to run through documents and webpages to weed out those small annoying and misleading texts.

Link has been removed here, as I now am wiser and found the story behind the store...

1 members found this post helpful.

People have lost the art of slack if they're worried about a website. A real slacker prefers to keep it the way it is. Outdated, confusing and inaccurate. In Slackware inertia is the greatest of the beatitudes, and making converts is the last thing we want.

3 members found this post helpful.

Haha, amen on that!

Laughs aside, I like my Linux experience to keep the elitism at a minimum personally.

I don't think slackware.com is all that confusing and is easy enough to use. Sure, an update will be nice, but it doesn't have to be any wizz-bang Web 2.x crap. Simple static HTML/CSS is all that's really needed to keep folks updated and informed. As for hand modification - why not? This too can be automated with a shell script.

Heck, if I had my way, I'd drop the current site in favor of gopher://slackware.com. Now THAT would be truly slacker retro!

2 members found this post helpful.

Heh! Ah... the memories.

Man, you have no creativity. Nobody said anything about changing the theme, all you gotta do is have a little fun. Pat could put up a quick reminder on the main page to let people know that yes, we are, in fact, still here

I'll do it if nobody wants to. Nothing would be please me more than making obscure network protocol references that my generation doesn't know!

Attached Thumbnails

 

2 members found this post helpful.

Imagine the coming president candidate saying: Slackware is dead.

I can imagine Donald Trump saying that.

It's dead, a fact. Slackware is dead.

Attached Thumbnails