On 3/7/26 7:12 PM, Lydia Sobot wrote:
You'll need a WANTLIB line, and it would be nicer to use PORTHOME instead
of your custom TESTHOME. Creating .config under ${PORTHOME} makes a few more
tests pass for me, when testing with privsep enabled.
Noted, I think I took the TESTHOME pattern from another port but I
forgot where from, but also if I may, what purpose does WANTLIB serve
here? In general actually I spent much more of my time trying to figure
out how to make the ports framework cooperate with me adding crate
dependencies with licences and all that rather than actually making the
program compile
From a bit of testing, starship is quite neat - not necessarily for ksh purists,
but I'm quite enjoying it in combination with fish and work with git repos (no
support for jj yet, at least not out of the box).
With Lydia's tarball and the attached Makefile, ok volker@ if anyone else is
interested.
COMMENT = minimal customizable cross-shell prompt
V = 1.24.2
DIST_TUPLE += github starship starship v${V} .
CATEGORIES = sysutils shells
HOMEPAGE = https://starship.rs/
MAINTAINER = Lydia Sobot <[email protected]>
# ISC
PERMIT_PACKAGE = Yes
MODULES = devel/cargo
MODCARGO_NO_DEFAULT_FEATURES = Yes
MODCARGO_FEATURES = notify
CONFIGURE_STYLE = cargo
TEST_DEPENDS = devel/git
PORTHOME = ${WRKSRC}/testhome
WANTLIB += ${MODCARGO_WANTLIB} m
pre-test:
mkdir -p ${PORTHOME}/.config
.include "crates.inc"
.include <bsd.port.mk>
