Date: Thu, 17 Mar 2022 19:18:37 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 262628] devel/php-composer2: Update to 2.2.9 and question for future versions Message-ID: <bug-262628-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D262628 Bug ID: 262628 Summary: devel/php-composer2: Update to 2.2.9 and question for future versions Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: madpilot@FreeBSD.org CC: cyberbotx@cyberbotx.com Flags: maintainer-feedback?(cyberbotx@cyberbotx.com) CC: cyberbotx@cyberbotx.com Created attachment 232527 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D232527&action= =3Dedit 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 nami= ng) 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 ri= ght away once 2.3.0 is final. What do you think? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-262628-7788>