Re: git: 988da7290c99 - main - ./UPDATING: mention the python default version change
- In reply to: Charlie Li : "Re: git: 988da7290c99 - main - ./UPDATING: mention the python default version change"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 04 Jun 2024 07:42:50 UTC
On 04.06.24 06:20, Charlie Li wrote: > Baptiste Daroussin wrote: >> I am not saying that allowing concurrent version is a bad idea, but in >> that area >> php packaging does a better job, I have no idea what is supposed to >> make sense >> in the end, but the current situation is clearly unfriendly to any >> package >> manager. >> > I actually have this issue with explicitly installed PHP packages here too. Indeed. But after years of seeing FreeBSD usage parallel to various Linux Distributions and Windows Versions: i like the FreeBSD way best. While it involve stuff like pkg set (or a simple script like grep the pkg packages, do a search & replace and than do pkg delete + add), it is a consistent way you can also automate. PHP Updates are very smooth in comparison to other plattforms. Also it seems like a crazy "i can not believe this" fact, when we say, we have actually all supported PHP versions with just a simple "install it". No Third-Party-Repos, no compilation, no hacking. >> There is a reason why on most linux distros they do support only one >> major >> version of python for packaging and encourage users to use virtual env >> or alike >> for other versions, I am not saying we should do that, but we need to >> find >> something that is upgrade friendly and do not rely on hacks like pkg set. >> > virtualenvs are encouraged in the Python ecosystem regardless of any > operating system distribution considerations, but the ability to use > different Python interpreter/distribution versions still hinge on having > them and requisite packages available in the system. Indeed! Best, Torsten