do not edit — generated by btf.
git.druid.rocksindexdruid520portssysroots/newbase.conf

sysroots/newbase.conf


# the "biased, almost-GNU-and-C++-free" druid520 base rebuild: build
# every replacement package (sbase/ubase/mksh instead of busybox,
# u-config instead of pkgconf/pkg-config, bsdpatch instead of
# gnu-patch, byacc/sinit/perp confirmed as-is, curl+mbedtls, and
# whatever the tcc-vs-chibicc call lands on) into this fully isolated
# root first -- verify the whole thing actually works together as a
# coherent system before "mp sysroot install newbase" folds it onto
# the live root in one deliberate step. see reference/commands/
# sysroot's own docs for the fold mechanics. openrsync/rsync dropped
# from this plan entirely -- nothing in this tree ever depended on
# rsync in the first place, so there's no reason to drag in bmake
# (openrsync's own build-tools/bmake dependency has its own real,
# separate NetBSD Makefile.boot architecture-misdetection bug) just
# for a standalone tool nothing needs.
MP_PREFIX="/var/mp-newbase"
 
# this sysroot's own %shell/%coreutils/%patch defaults -- unset, these
# would resolve to busybox (lowest pkg_pref of the bunch), which hard-
# conflicts with sbase/ubase (see their own pkg_conflicts) the moment
# both are wanted in the same install request. this sysroot never
# installs busybox at all, by design.
TARGET_shell=shells/mksh
TARGET_coreutils=coreutils/sbase
TARGET_patch=sysutils/bsdpatch
TARGET_pkg-config=build-tools/u-config
TARGET_yacc=build-tools/byacc
# %libc/%cc: this sysroot only ever gets FOLDED onto the already-fully-
# populated live root -- it never needs its own musl/gcc copy just to
# satisfy GLOBAL_DEPS' automatic %libc append (hit for real: musl got
# silently pulled in and built here, a pure waste, and its own merge
# also hit a real, separate mpx merge.c bug on a directory-tracked
# manifest entry -- worth fixing properly later, avoided here by
# simply never building a redundant musl into this sysroot at all).
TARGET_libc=meta/null
TARGET_cc=meta/null
 
# sbase and ubase each independently implement a couple of the same
# utilities (dd, mknod) -- real, expected overlap between two
# independent suckless projects, not a bug in either. sbase wins
# (it's the %coreutils default here); ubase's own install still
# succeeds overall either way (mp.git 26286e3's own fixed
# CONFLICT_PRIORITY), just excluding those two paths from its own
# manifest.
sbase:
	CONFLICT_PRIORITY=100
ubase:
	CONFLICT_PRIORITY=10
 
powered by btf.