4 ms·
> At least if folks use something like Symfony or Laravel it's harder for them to shoot their foot off I'd like to consider giving Symfony or Laravel a try, bu
by tzs 6y ago
> At least if folks use something like Symfony or Laravel it's harder for them to shoot their foot off
I'd like to consider giving Symfony or Laravel a try, but at work we run Debian and stay with a given release until it is near the end of extended long term support.
Laravel's oldest release that is still supported is 5.5 LTS, which requires PHP >= 7.0.0. The next oldest still supported is 6 LTS, requiring at least 7.2.0.
We're on Debian 8, Jessie, which is on extended long term support until 2022. It has PHP 5.6.29, so no Laravel for us. Even if we were on 9, Stretch, which has PHP 7.0 and so could use Laravel 5.5 now, Stretch is on long term support until 2022 and will be on extended LTS for probably a couple years after that, we'd run past Laravel's LTS.
Heck, even if we were on the current Debian, which is 10, Buster, which has PHP 7.3, it is not clear we could use Laravel. Laravel only does security fixes for 3 years on LTS releases. Buster has Debian support until 2024, LTS for a couple years after that, and then extended LTS for a couple year, so it will be past the end of security patches for the current Laravel before it even reaches LTS.
So unless I can be sure that the next LTS release of Laravel does not raise the PHP requirement past 7.3, Laravel is out of the running.
(But wait...what about https://packages.sury.org/php/ https://packages.sury.org/php/ which is a package repository maintained by one of the main Debian PHP packagers where he packages newer PHP for older Debian? That's close enough to the official packages that I could probably convince the IT folk to add it. Alas, he only packages for older Debian until they go out of LTS. If you stick with it through extended LTS, you are out of luck).
With Symfony, 3.4 is the oldest supported release. That requires at least PHP 5.5.9, so will work on Jessie or later. However, 3.4 support ends in a couple months. That will leave all supported Symfony requiring at least 7.1.3 which means you have to be on Buster. It looks like they have a similarly short LTS support life as Laravel, so even if you are on Buster today, there doesn't seem to be any good reason to believe that there will still be a supported Symfony that works there at the end of its regular support lifetime, let alone that one that can take you into Buster's LTS or extended LTS.
Debian is the only Linux distribution for which I've looked at this in detail, but a brief look at others suggests that the situation is similar for Red Hat, and maybe Ubuntu.
- conradfr 6y agoThat's more a problem with the way you workplace operates, as even the php organization doesn't support versions < 7.2 (and more realistically < 7.3). You're kind of in a no-win situation.
- tzs 6y agoDebian LTS for a given Debian release provides support for whatever packages came with that release even if the upstream does not. They are still patching PHP 5.6 on Jessie and 7.0 on Stretch. There was a 5.6 update on Jessie last month. See https://security-tracker.debian.org/tracker/source-package/php5 https://security-tracker.debian.org/tracker/source-package/p... for a list of all Debian's PHP 5 patches. The latest dozen or so are all less than a year old.
- conradfr 6y agoThat's great for legacy projects but not realist for new or active projects running on modern frameworks.
- troyvit 6y agoI think you just said what OP said, but backwards. They have a long-running stable system that works great, but because the frameworks require versions that are more bleeding edge they aren't going to get them. I think frameworks that always target newer versions of their base language are limiting who will use them.
- rbg246 6y agoAre you not allowed to install a new version of PHP? Because isn't it more worrying that you are using versions of PHP that are EOL?
- tzs 6y agoThey are EOL upstream. LTS Linux distributions backport security fixes and some bug fixes from current upstream versions to whatever versions are in their distribution. That's actually one of the main points of an LTS distribution. They run the same version of languages, databases, web servers, firewalls, and everything else at the end that they did at the start, so that you get a stable platform throughout their lifetime. If you go down the road of updating individual components to something significantly newer than what your distribution supports you can easily end up breaking other things--so then those need to be updated too, which might break more. Even if that doesn't break anything else (and PHP would probably not...offhand I can't think of anything that I need in Debian that depends on PHP so switching to a later PHP would probably be safe on that front), it leaves you with software that isn't covered by your distribution's regular updates. For each such thing you install, you've got to put in place some way to find when the upstream has a bug fix or security fix you need, and some way to get and apply that.
- rbg246 6y agoI didn't realise they backported security fixes for PHP(as the example) independent of the vendor thanks for that you massively upgraded my knowledge.
- Lazare 6y agoMmm. Worth noting that PHP as a language has been moving pretty fast lately. The 7.x series is something like 2-3 times faster than 5.6 in most benchmarks, plus a lot of developer friendly features have landed, and some useful security features, which has led to a lot of people cutting support for older versions. I understand the logic behind running Debian until the end of extended LTS, but it's going to have a number of drawbacks. Not being able to use a supported version of Laravel is probably not the biggest one either. It's not a tradeoff that would be viable for my team, at any rate.
- chrisandchris 6y agoYou could tell the same about (many) other languages or plattforms (e.g. .Net Core, maybe Java) Maybe only python2 will match your expectations.
- gremlinsinc 6y agoCan't you just upgrade to the latest debian, or switch to ubuntu? Seriously, migrating a php codebase is the easiest thing you could do. Of course you'd need to upgrade your code to php7 that isn't or may have breaking changes but the performance benefits alone are worth it. Maybe you should suggest to management that instead of staying till end of life you stay till one-half end of life, that way you still keep somewhat modern stacks.