[SOLVED] will slackware drop newer KDE versions or go systemd

Hi. Sorry (if you care) not reading or joining in past post #1 but first thought was there's always a spinoff, either from distro homes or by nature...

Originally Posted by ChuangTzu Rob.Rice, he is a dev. of his distro. Slint which is based on Slackware and Salix. Check it out, he is also a frequent poster on LQ and helps alot of people. Just a little FYI, systemd is not in Slackware now, will not be for the next few years, Alien is against it, PV also but is pragmatic. Who knows for sure, but I do know that we have resisted other poorly designed programs (PAM etc..), so I would imagine this would be no different. As stated by other people if PV and crew do add systemd, it will be the best utilized least maniacal and most sane interpretation in any distro.

I get the impression that Didier Spaier thinks
I have no right at all what so ever to ask this question ( I think I do )
I've just reread this whole thread and I see nothing that even comes close to a flame war ( except for my post to Didier Spaier and his posts about this thread )

so my question has been answered with a comforting NOT ANYTIME SOON
I will mark this thread solved
final note if systemd ever becomes part of slackware I will jump ship rather than have it running on my computer

You sucked me in... (couldn't leave this as just your "Rep:":) if you're not a developer or higher-up tester, who cares‽

Do people who "hate" systemd cook bread on their box? HAha...

Originally Posted by rob.rice I get the impression that Didier Spaier thinks I have no right at all what so ever to ask this question ( I think I do )

I think his frustration comes when you post it on several threads and then create a new thread to discuss it further. The majority of Slackers don't like systemd either and for those of us who've been on the forum for a long time, we see relatively peaceful periods of time without discussing systemd, then someone decides to suddenly freak out about systemd and start posting all sorts of things about it on the forum (especially when you link to a blog that is over a year old -- that's forever in Linux software time).

So, while you are of course free to ask your question, if you did a simple search for systemd in this subforum, and did a little research, you would've found that there's no reason to ask your question, because it's already been answered many times before in this forum.

We just don't like to see it constantly brought up. Slackware doesn't currently include it and there's no signs on the horizon that it will need to include it. So there's no reason to start worrying about it getting included in Slackware. Which means there's no reason to start posting about systemd in Slackware. We just don't want to see it...

And it isn't as easy as "just ignore the thread", because I frequent this forum many times throughout the day and I like to see all the threads as read. First world problems... I know

And all of us regulars take pride in the distro and in the support we provide to the community. Sometimes our verbiage may come across as being a part of the Slackware team, but most of the time, it is more part of the community that provides support to Slackware. And many of us have been around long enough to have a pretty good idea of what Pat will and won't do (although, he does occasionally change things up on us), and we will sometimes offer that idea to people on the forum (because Pat doesn't answer everyone).

for me and I doubt I'm alone in this
this sub forum it the best to find information about slack
and how would I go about researching the question
"will slackware include systemd any time soon ? as of today"

yes this question has been asked here BUT has it been asked lately

there is no slackware blog Pat is working on slackware
he doesn't have time to blog or he dosen't like to what ever
I don't expect Pat to keep us informed
nether do I want to bother hem with a PM to ask that question
about the only PM I would bother Pat with is a
thank you for all his good and freely given work on slackware

I seriously doubt I could start a flame war HERE by bashing systemd even if
I wanted to
posting in support of slackware including systemd that would start a flame war

if this question is so tiresome that it can't be asked
how about a closed sticky thread stating
slackware will not include systemd any time soon
everybody can count on this question coming back up
not by me but it will be coming back up
maybe as soon as this thread falls off the first page of this sub forum

http://www.sc.edu/beaufort/library/p...es/bones.shtml
http://lmgtfy.com/?q=will+slackware+...+any+time+soon
the truth is out there google it

Tost?

My question has been answered
can I request this thread be closed
will the mods do that for me if I as the OP ask ?
is there anybody who would oppose this thread being closed

I'm sure they will @BHs... as a 3rd shift GNU\Linux user tho I must say chipping in is change, evolution happens or don't use technology...

You can search using the forum's built in search and you can restrict the results to the Slackware subforum.

But it wasn't so much that you asked this question (at least for me), it was that you posted systemd related things on several topics (1 2 3 4 5)... expressing your disdain for that software. We get it, you don't like systemd. Most of us don't either, and we don't need to read 5 different posts from you in random topics about how much you dislike it and then a whole new thread on the subject.

And if it were to ever get added, I doubt there'd be much discussion from the Slackware team with us before it happens. They'll discuss it internally and if they decide to throw the switch, it will show up in the changelog and we'll have a ton of people venting in the forum (just like pulseaudio). We'll find out the same time the world does... in the changelog. I doubt they'd post a sticky covering this info.

And finally, they usually don't close thread unless there is some major flamewars or bashing going on, but you can try to click the "report" button on your post and request it and see what they do.

Originally Posted by rob.rice I have a question for you Didier Spaier would you like to see slackware jump on the systemd band wagon ? from your replays in this thread it looks like you would

Maybe this post made you think that, but it was just to indicate how someone could use systemd with Slackware if so inclined. Maybe I misunderstood your initial post and didn't realize that you just wanted to state your dislike for systemd. This kind of misunderstanding sometimes happens to me because I am not a native English language speaker.

I won't answer your question. If/when PV decides to make this jump I will assess the consequences for the Slint project, but I have neither pretension nor desire to have any influence on his decision.

Originally Posted by montagdude Anyway, if you are wanting to make a list of dependencies, sbbdep is a good place to start. One caveat is that I don't think it picks up dependencies in interpreted languages like python, because the dependency information is only contained in the source code for those.

nomen est omen:
Slack Build Binary Dependencies

Originally Posted by a4z nomen est omen: Slack Build Binary Dependencies

Ah, I didn't realize that's what the name stood for.