Date: Sat, 05 Nov 2022 07:18:35 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 267501] x11-wm/nscde: Replace expired ksh2020 dependency, Remove DEPRECATED Message-ID: <bug-267501-7788-t9FeWVTDeW@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-267501-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-267501-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=3D267501 --- Comment #3 from Chris Moerz <freebsd@ny-central.org> --- (In reply to Kubilay Kocak from comment #2) thanks, you're making a fair point in regards to ksh. Basically, upstream nscde requires $PREFIX/bin/ksh93 to run. Originally, it even required it during build, which I assume can be relaxed since it switc= hed to autotools (though I have not tested that yet). Upstream nscde does not make any assumptions about which ksh it needs to be= - at least not to my knowledge. I originally chose ksh2020 because it appeare= d to be the most recent version. In hindsight, this might have been a mistake. After the port's first iteration, I realized during some experiments that ksh2020 did not compile on arm64. So I added the option to switch between ksh2020 and ast-ksh, because I wanted to make it work on arm64 without breaking/reinstalling it for existing installs on amd64. When I saw the deprecation notice, I figured it would be best to move the w= hole port to a ksh port that will remain stable. Admittedly, this will cause reinstalls for those on ksh2020 and ast-ksh. I'm a bit unsure what the "best practice" is in such a situation - obviousl= y, there could be numerous different ksh ports. Should I include options for a= ll available ksh ports (except the deprecated ones, obviously)? I also understand, I should probably use the opportunity to investigate, whether it's possible to remove ksh from the build dependency list? Appreciate your inputs! thanks br chris --=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-267501-7788-t9FeWVTDeW>