Date: Mon, 10 Mar 2025 21:08:11 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 285291] devel/esbuild: latest version break net-im/signal-desktop Message-ID: <bug-285291-7788-0eL9FoHf1M@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-285291-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-285291-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D285291 Dave Cottlehuber <dch@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open --- Comment #2 from Dave Cottlehuber <dch@freebsd.org> --- Sure, that's very reasonable. This is the first time I've been informed it was broken BTW. When (in 2021) this port was added, there were obviously no consumers, and it was used as a local web-dev tool. Keeping it as up-to-date as possible has been my main objective, that's typically how web dev goes. I have no idea when it was added as a dependency, nobody informed me, so it's not unreasonable (from my perspective) that I don't know that it's now become an essential dependency for building signal. https://www.freshports.org/devel/esbuild/ says its the only consumer, I'll happily test it in future, I can only do this on amd64 though. When esbuild is updated, is it sufficient to bump the ESBUILD_VERSION in net-im/signal-desktop/Makefile and try to rebuild? When you next update net-im/signal-desktop, let me know and we can bump esbuild concurrently. Would that work for you? --=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-285291-7788-0eL9FoHf1M>