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.
Is that really a good idea? I'm just thinking of how long it took to get things ported away from php-5.6. If php-8.0 can *replace* php7 and nobody would complain, then I'd agree that we should do it.
Thanks for your reply, Patrick.
Well, the interpreter itself has the lifecycle disclosed here. 7.4 has 9 months left of active support and 1 yr and 9 months of security patches. On the other hand, php8 has 1y9m of active, 2y9m of security patches ahead.
All major php frameworks (i.e. WordPress >5.6, Drupal >9.1, Laravel >6 and many others) are already compatible with php8. Most of the legacy code requiring php5.6 will not run on php7.4 anyway. IMHO, and speaking as a PHP developer myself working with both up to date frameworks and legacy code, I see php8 landing in Slackware as a good thing.
If you want to be on the safe side, maybe you can add php8 as the default one and php7.4 in extras or testing, or the other way around. I don't know how much overhead this poses to you, but it looks like quite a safe upgrade path to me. If this is much work, I do not oppose to php8 landing now to replace 7.4 altogheter, as I already have the need to manage all the way down to php5.6 so legacy code can run.
Yes, my most recent apps may require some coding so they can run on php8, but this is really a minor effort to a much brighter, longer and supported future. I for one support this move.
Last edited by denydias; 02-15-2021 at 10:53 PM.
Reason: typo, mention testing.
Wondering if the 'store' will have DVD's available.
Does the store even exist anymore?
I have a collection of the DVD's from version 7 forward still in the original shrink wrap would like to keep it moving forward.
Probably worth a 'lot-o-money' some day. LOL
john
I don't think so. Most if not all of us cancelled our Slackware subscriptions after we learned about how badly Patrick was being ripped off by the store.
I will continue to make an annual donation to Patrick. We're now at Alpha status I suspect a beta release is coming.
Just finished updating my main driver. It was a breeze!
That move from Mon Feb 8 05:13:26 UTC 2021 changelog (glibc-solibs > aaa_glibc-solibs and aaa_elflibs > aaa_libraries) proved to be a very smart one. Those rare glibc-solibs glitches when such a massive upgrade occurs now belongs to past.
I would like to thanks PV, all the dev team and their supporters over the years for making Slackware my fist OS choice for more than 25 years. Let other 25 years comes ahead as stable and free as it was until now!
Thanks PV and team . Just putting the finishing touches on the update to 15.0 alpha 1 and so far so good; I did not fall in a hole this time with the glibc updates! 15.0 is indeed going to be an incredible release...
Well, the interpreter itself has the lifecycle disclosed here. 7.4 has 9 months left of active support and 1 yr and 9 months of security patches. On the other hand, php8 has 1y9m of active, 2y9m of security patches ahead.
All major php frameworks (i.e. WordPress >5.6, Drupal >9.1, Laravel >6 and many others) are already compatible with php8. Most of the legacy code requiring php5.6 will not run on php7.4 anyway. IMHO, and speaking as a PHP developer myself working with both up to date frameworks and legacy code, I see php8 landing in Slackware as a good thing.
If you want to be on the safe side, maybe you can add php8 as the default one and php7.4 in extras or testing, or the other way around. I don't know how much overhead this poses to you, but it looks like quite a safe upgrade path to me. If this is much work, I do not oppose to php8 landing now to replace 7.4 altogheter, as I already have the need to manage all the way down to php5.6 so legacy code can run.
Yes, my most recent apps may require some coding so they can run on php8, but this is really a minor effort to a much brighter, longer and supported future. I for one support this move.
Not all applications are ready for migration to PHP 8!
Eventually PHP 8 in /testing.
As I was logging in to the forum, I noted that my cron job was running, starts at 16:00, it already finished! Wow, was not expecting that. Next step log on a do the deed. Eggcited for sure.
Hmmm since Slackware Current (testing release) is more stable than most distro's "rock solid stable" as well as newer and generally faster. Why would I care that Alpha could take months to go Beta and more to go Full Release? Whether you update daily or run Current as a snapshot, Current is awesome! Alpha is just Mo Betta. We rollin'.
I thought of a scene from Tomb Raider, as releasing a distro version has a lot to do with planetary alignment (planets = the major upstream software projects)
edit: and yes, sometimes it takes years for an alignment to happen xD
Last edited by Martinus2u; 02-16-2021 at 03:19 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.