Created attachment 232527 [details] Update patch Hi, I'm attaching a patch to update composer to latest version, 2.2.9. At the same time I noticed a new 2.3.0 release candidate is being tested upstream: https://getcomposer.org/changelog/2.3.0-RC1 Looks like it could have incompatibilities and upstream seems to suggest 2.2.x should be kept around for a while. As maintainer do you have a plan for it? We could move current composer 2.2.x to a devel/composer22 (or similar naming) port and keep composer2 updated to 2.3.x, or maybe also move main port to composer23. If you feel confident we could also just drop 2.2.x and update composer2 right away once 2.3.0 is final. What do you think?
Looking at what it says in the changelog of 2.3.0-RC1 and it saying the minimum version is PHP 7.2.5, and that FreeBSD's ports tree only has PHP 7.4.x and later, I'd say it should be fine in the future to keep 2.3.0 under devel/php-composer2 instead of making a new port. That being said, patch to 2.2.9 looks good to me.
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=13aa45453f3a4e524185ada8c695314861692ca7 commit 13aa45453f3a4e524185ada8c695314861692ca7 Author: Guido Falsi <madpilot@FreeBSD.org> AuthorDate: 2022-03-17 21:55:58 +0000 Commit: Guido Falsi <madpilot@FreeBSD.org> CommitDate: 2022-03-17 21:57:29 +0000 devel/php-composer2: Update to 2.2.9 PR: 262628 Approved by: Naram Qashat <cyberbotx@cyberbotx.com> (maintainer) devel/php-composer2/Makefile | 2 +- devel/php-composer2/distinfo | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-)
Patch committed. Thanks for the feedback!