While everybody has roadmaps, even the KDE Software, looks like the Slackers had been invented a new occult science: Changelogology, the art of guessing the future into ChangeLog.

I am not sure if I should laugh or cry...

2 members found this post helpful.

Maybe you're not that old to remember that, but changelog is de facto method for Slackware since July 17, 1993. This is way before roadmaps become something in software development and 15 years before github issues hit the wild to become common place.

Slackware's changelog works pretty nice IMHO. Steady as the product it defines. Nothing to complain here. It even brings hints!!!

And yet, if BDFL decides to move to something more fancy, I see absolutely no problem to accept such change.

I don't know about you, but I have all the reasons to smile.

3 members found this post helpful.

I sure hope so. It sure looks like another step in the direction of integration into the next "release" of Slackware.

Happy Slacking, y'all!

1 members found this post helpful.

Hi @All,
can someone kindly direct me where to find ru_RU formats for time, numbers and so on in plasma 5 desktop for slackware (having current installed from Alien Bob live iso (great work, btw), for some not apparent reason I see only cv_RU, ba_RU, and myv_RU. I have no idea what these locales/formats stand for, because my native language is Russian and locale/formats are supposed to be ru_RU). Language layout switch works normal. I just want 24h time format and comma for digits, but ru_RU is missing in drop down lists in formats setting.

Thanks in advance.

This week's bug fixes,

https://pointieststick.com/2020/10/3...-bug-massacre/

Hi there, I overlooked that option "ru_RU" is listed in Russian literally ("Россия(ru_RU)"). "Problem" solved, sorry for false alert.

Good things

2 members found this post helpful.

Not every project has roadmaps and that isn't a bad thing. Roadmaps are handy when the developers know exactly where they want their product to end up. It can also introduce hard deadlines that can lead to either pushing out software before its ready or delaying things when development doesn't go as expected. It introduces a large amount of stress to the dev team. Slackware has never been that way. Sure, we might see hints in the changelog or in Pat's posts, but Pat doesn't like being held to a public list of what should happen and when.

If Slackware development isn't to your liking and you feel a roadmap is necessary, then maybe it's time to look at other distros that better match your development desires...

Why I like Slackware: Everything just works! No need for deadlines or roadmaps, things are upgraded only when they work for everyone using Slackware, from production environments to home enthusiasts, 32-bit and 64-bit cpus. I ran Slackware in a major university for redundant DNS, mail and web servers, including remote learning for the Nursing college with tens of thousands of graduate students all over the US. "A new occult science" displays profound myopia and ignorance in the absence of facts. Me, I'm running plasma 5.20.0 and frameworks 5.75.0 on my workstation, but that's not yet ready for distribution; still needs automated source acquisition, automated build scripts for individual packages and all. Do volunteer to help if you are able.

I guess you talk about Slackware 14.2, right?

I really hope you use a rock solid stable version like is Slackware 14.2 in your business.

I feel that he does not talks about Slackware 14.2, but about Slackware-current.

The facts are that there's an absence of facts regarding what and when will happen the next things on -current, even with a rough precision of years.

Yeah, maybe is fun for waiting in the dark, or how some says: radio-silence, for one year or two, but now we are (as you known) in the fourth year and counting.

You wonder that the people starts to wonder if ever will be an end of this never ending development?

Congratulation! Me I run a full (re)build of Plasma 5.20.2 and such...

BUT, I seriously doubt that my cheap low power computer can be called "workstation" even with a serious amount of enthusiasm...

Then, please do not make people to believe that someone needs a "workstation" to build Plasma5.

In fact, is enough a crapstation like ones I have.

Seriously? As someone who built Plasma5 for hundred times and use it since years, I will love to hear your real arguments for. In fact this claim of yours made me to respond to your post.

Excuse me? About what you talk here? A personal wish or something similar?

From what I known, Mr. Hameleers' mega-builds never had this feature.

This starting with X.org build, then continuing with KDE4 build - both used from long time by Slackware on stable releases.

Every of those mega-builds needed the packager to manually download the source tarballs and to put them in the proper place. Take a look there:

https://slackware.uk/slackware/slack...ource/kde/src/
https://slackware.uk/slackware/slack...rce/x/x11/src/

Like you can see, the source tarballs was always shipped with those mega-builds.

I should note that automated downloading source tarballs seems to be considered a bad habit? Did you remember that anti-Rust thread?

Please! This claim just demonstrate that you talk politically, nothing more...

Hello! This feature exists since uncounted years!

If you need to build a single package, you just need to type:
This command will build only the KWin package on Plasma5.

BUT, I bet that similar commands works also with KDE.SlackBuild or x11.SlackBuild from Slackware 14.2 and even from the older releases.

I do not know others, but if Mr. Volkerding needs help for packaging Plasma5, I for one I volunteer for, me having some experience into building it.

However, permit me to doubt that he will need my help, when there are heavy builders like Mr. Hameleers and Mr. Workman.

So, your demand looks being just rhetorical.

2 members found this post helpful.

To be fair, if stable continues to meet a person's needs then they probably don't really care when -current comes out. I personally think that a 4 year (or more!) wait for a release is way too long for Slackware though (e.g., stable is still using unsupported OpenSSL libs).

I can't see how automated downloading is itself a "bad habit". If the packages are signed, what are the advantages of downloading manually over automating the process? Automating at least saves time but could be safer too, since people can get lazy and not be bothered to manually check signatures. But anyway, the point of the Rust thread was about not trusting upstream's binary bootstrap compiler (which applies whether or not you automate the download).

1 members found this post helpful.

It's bad to some people. SBo disallows it, but Pat has SlackBuilds that download during the build process and many others have SlackBuilds that will download tarballs when running.

And I think hpfeil was talking about automating the download of the plasma5 source tarballs from KDE servers. Automated download of the ktown source tarballs is handled with the rsync command Alien provides and automated downloads of ktown packages can be done with slackpkg+.

And I am one to write a lot of text, but man, off hpfeil's little paragraph, you went crazy in depth. Wow! I think you read waaaaaay too much into what was written.

Russian or Chinese, they are all very welcome here, and they express themselves very well in English, which is to them a foreign language. If the constant targeting of these nationalities in a passive-aggressive manner was the other way round and Americans were the target the mods would have stepped in long ago, as indeed I distinctly remember them doing on one occasion.

1 members found this post helpful.

What exactly is this in reference to?

2 members found this post helpful.

Perhaps you can extend a helping hand to an old fool who is having difficulties? Using the alldeps.SlackBuild ends with an error at qjson. Have tried to find out the answer by myself but have no idea how to proceed.

1 members found this post helpful.