Spin off from 'What version of Python 3.x should ship with Slackware 15.0?'
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.
It is about python version in stable release. Not -current. I can imagine that stable 15.0 will be shipped with python 3.9 while -current with 3.10. For reasons you posted.
But we aren't on a stable release for 15.0 yet. We don't even know how long it will take until 15.0 stable is released. It could be a few weeks or a few months (and hopefully not a few years ). Right now, -current is still -current, and that includes the possibilities of breakage. Previous release candidates for previous releases of Slackware had shared library .so bumps (14.2 saw 3 poppler bumps and an ntfs-3g bump after RC1 was announced, and this was before Eric had his poppler-compat package, so it broke LibreOffice for everyone who used his packages), so this certainly isn't unique.
Why not have the latest stable Slackware be on the latest stable python3 release? Just because some things are broken on SBo? Most of those will probably just need a version bump. If upstream doesn't already support 3.10, if they have any decent development activity, it will likely have support before 15.0 is stable.
Will this cause growing pains? Yes. Will 15.0 be better off in the long run by including 3.10? I believe so.
Speaking for myself, I use Slackware in my business every day. In combination with other technologies, I have found it to be bulletproof. I'd use Slackware before any others because it doesn't bring the baggage that all of the others carry.
You're welcome to have this opinion, but please don't present it as fact.
Of course you realise that all of the *BSD maintainers are hobbyists, right??
Sorry if I presented my opinion as fact. Of course what I say is my opinion only.
As I understand that when you say
Quote:
Originally Posted by rkelsen
Of course you realise that all of the *BSD maintainers are hobbyists, right??
Slackware may be oldschool, but thankfully it is a school. The point of slackware is learning what's under the hood: by the time you graduate, the rolling release feel to -current is but the gentle swells of the sea while steering your custom vessel.
Slack is KISS no more no Less if Pat want's to mess with stuff so be it. He got lazy should have delivered 15.0 with gcc 8.5 but he got lazy simple fact we all in the community and so did Eric Hameleers have a stable kde5 for 8.5 GCC.
Pat screwed up he just human.
Now he is screwing with the base the people try to use the tool because 14.2 is ancient.
But we aren't on a stable release for 15.0 yet. We don't even know how long it will take until 15.0 stable is released. It could be a few weeks or a few months (and hopefully not a few years ). Right now, -current is still -current, and that includes the possibilities of breakage. Previous release candidates for previous releases of Slackware had shared library .so bumps (14.2 saw 3 poppler bumps and an ntfs-3g bump after RC1 was announced, and this was before Eric had his poppler-compat package, so it broke LibreOffice for everyone who used his packages), so this certainly isn't unique.
Why not have the latest stable Slackware be on the latest stable python3 release? Just because some things are broken on SBo? Most of those will probably just need a version bump. If upstream doesn't already support 3.10, if they have any decent development activity, it will likely have support before 15.0 is stable.
Will this cause growing pains? Yes. Will 15.0 be better off in the long run by including 3.10? I believe so.
Pat had a chance like all distros delivered Kde5 with gcc 8.5. we should be on 15.1 right now he just got lazy . Eric did all the work for him. KISS. everyone had a stable kde5 with gcc.8.5.
His blob let the leader play with it.
Pat had a chance like all distros delivered Kde5 with gcc 8.5. we should be on 15.1 right now he just got lazy . Eric did all the work for him. KISS. everyone had a stable kde5 with gcc.8.5.
His blob let the leader play with it.
Eric did a lot of work (almost all the work for Plasma5), but it's pretty messed up to diminish everything that Pat has done. This development cycle has been one of the busiest ever. Someone posted the averages of changed packages per day, and this cycle is the largest. Even more impressive when you realize we were stuck on KDE4 for YEARS and those packages pretty much never changed.
Almost 40,000 25,000 package changes (38,56424,247)! (EDIT: My math was way off... not sure what happened since kcalc doesn't have a history.)
Pat's hardly been standing by while Eric was churning out ktown updates. I don't understand how you can consider him lazy just because he didn't push out a release when he felt it wasn't ready. The ChangeLog shows he hasn't been lazy.
Not to mention, we had two full rebuilds during this cycle and he even helped support SFS (Slackware From Scratch) during this cycle.
Should we have had a 14.3? Yes, with proper hindsight to how long this development cycle would be, I think everyone (probably even Pat) would agree that there should've been at least one interim release, but it's impossible to know that at the beginning or even the middle of a dev cycle.
It seems you aren't happy with how Slackware development is handled by Pat. Maybe it's time for you to fork or find another distro that is more to your liking...
Last edited by bassmadrigal; 10-22-2021 at 04:51 PM.
Slack is KISS no more no Less if Pat want's to mess with stuff so be it. He got lazy should have delivered 15.0 with gcc 8.5 but he got lazy simple fact we all in the community and so did Eric himler have a stable kde5 for 8.5 GCC.
Pat screwed up he just human.
Now he is screwing with the base the people try to use the tool because 14.2 is ancient.
Too bad the little question on each post asking "Did you find this post helpful?" no longer has the "no" option.
Too bad the little question on each post asking "Did you find this post helpful?" no longer has the "no" option.
Why, you could have used it upon this one!
That was a wish list for me and My project. all the other disto's did this. But Patrick. This proves my point.
Unlike you Richard I selected this tool Slackware to compile my projects. And My projects have to span all distro's
.
You keep doing your thing and be kind to the people. I will just use the tools That I create. I have a slackware-14.2 that is so customized
it it looks like Ubuntu 18.04.Kinda looks Like Eric's the one he builds chromium with.
He spoon fed you, shame you did not use the stable work. It was on an iso image every week. Where you Have Been Richard.
Last I remember there was never enough blotter for you. Just put in jello and use it like window pain.
That's a dark star.
why would we need this. https://mirrors.kernel.org/slackware...lackware-14.2/
What did gcc 8.5 and 9.2 have in common.
Why would people need a newer gcc for slackware 14.2
GLIBC did not have pthread but the GCC did.
Are we tripping yet.
Quote:
Bass
I am sure Pat can speak for him self explain why we went from gcc 5.50 to 11.20. I am sure he can explain all this.
I am sure he will. But the change log shows it. Lazy is my term. because the changelog shows it.
We all get lazy I am one to be that way at times.
15.0 wether kde5 or not with 8.5 gcc that was a stable platform. or the 9.2 gcc that spwaned many stable systems. I am sure. Pat can explain.
a Release is a line in the sand. Hard to draw it.
Slack is KISS no more no Less if Pat want's to mess with stuff so be it. He got lazy should have delivered 15.0 with gcc 8.5 but he got lazy simple fact we all in the community and so did Eric himler have a stable kde5 for 8.5 GCC.
Pat screwed up he just human.
Now he is screwing with the base the people try to use the tool because 14.2 is ancient.
I just reported this post. Hope LQ will do something to prevent similar posts to appear.
I just reported this post. Hope LQ will do something to prevent similar posts to appear.
Does this have anything to do with the OP. Because base system is just that. That is Pat;s Hobby last I looked . Messing with the base or as a screw your turn it to make it different. your mind I hope should be nicer.
If you do not Turn the screw or tighten the project. I hope you do not think I was thinking of a slang term.
If I was you please be kind and stick to the OP.
My Father took enough abuse in here I am not going to deal with this type of outbreak. The OP makes a fine point could you reply to the matter.
Your lucky I am not my father. He lost his youngest son in Afghanistan Which was my younger brother.
I am sure he was very unstable at times. But do not confuse me with what I say and do.
Be kind carry on. Glad you had a vote.
Your lucky I am not my father. He lost his youngest son in Afghanistan Which was my younger brother.
I am sure he was very unstable at times. But do not confuse me with what I say and do.
Be kind carry on. Glad you had a vote.
I am sorry for your brother. I marked red in my post reason for report. Just search internet for "himler".
Slack is KISS no more no Less if Pat want's to mess with stuff so be it. He got lazy should have delivered 15.0 with gcc 8.5 but he got lazy simple fact we all in the community and so did Eric himler have a stable kde5 for 8.5 GCC.
Pat screwed up he just human.
Now he is screwing with the base the people try to use the tool because 14.2 is ancient.
Quote:
Originally Posted by lovemeslk
Does this have anything to do with the OP. Because base system is just that. That is Pat;s Hobby last I looked . Messing with the base or as a screw your turn it to make it different. your mind I hope should be nicer.
If you do not Turn the screw or tighten the project. I hope you do not think I was thinking of a slang term.
If I was you please be kind and stick to the OP.
My Father took enough abuse in here I am not going to deal with this type of outbreak. The OP makes a fine point could you reply to the matter.
Your lucky I am not my father. He lost his youngest son in Afghanistan Which was my younger brother.
I am sure he was very unstable at times. But do not confuse me with what I say and do.
Be kind carry on. Glad you had a vote.
So, did you think that your business background and the sad family story entitles you to insinuate that a particular Slackware Team member is the Reichsführer-SS of Slackware, just like YOU did?
I do NOT think so, even there's the saying: who forget his History is doomed to repeat it.
Last edited by LuckyCyborg; 10-20-2021 at 05:28 AM.
So, did you think that your business background and the sad family story entitles you to insinuate that a particular Slackware Team member is the Reichsführer-SS of Slackware, just like YOU did?
I do NOT think so, even there's the saying: who forget his History is doomed to repeat it.
Yes I seen his name many times on the changelog. Are you here to troll me or do you have anything to say that would help the forum.
Quote:
@Battered Fish: "They are wasting their time and ours. Instead of this distraction they could concentrate on getting a Slackware release every year instead of 5 years and counting."
I totally agree with your opinion.
I'm just a 'dumb' user, and if I don't like the way Slackware has been heading for the past few years, well then I can always fork off - yes I know that. But is Slackware targeted for a fan base or a user base? Let's just make that clear. Does Slackware want to become a rolling test release? Ok then just tell us so we'll know. If Slackware is meant for the tinkerer only - fine but at least tell the user.
you like to direct your response to the op. Seems his opinion was the start.
or are you fine trolling me .
This type of outrage is not good for you . Please be kind and reply to the OP opinion.
Yes My family has hurt enough.Especially My Father.
Eric Hameleers is completely another person, living in another Era - hard to confuse them, unless YOU insinuate things.
I thought you was speaking of Richard one of the team Dev's Lucky cool down deal with the thread.
It is about where is the base and is slackware a rolling thing now. Simple stuff.
Stop trolling me. Plz.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
). Right now, -current is still -current, and that includes the possibilities of breakage. Previous release candidates for previous releases of Slackware had shared library .so bumps (14.2 saw 3 poppler bumps and an ntfs-3g bump after RC1 was announced, and this was before Eric had his poppler-compat package, so it broke LibreOffice for everyone who used his packages), so this certainly isn't unique.
