Steffen's CRUX-Linux ports

A few ports for ∞ Crux-Linux that i miss. These are verifiable with my ∞ Signify public key. (Its signature: https://ftp.sdaoden.eu/stenur.pub.asc.) The ports can be accessed through the usual ∞ Crux port drivers, namely ∞ httpup (ports/stenur.httpup) and ∞ git(1) (ports/stenur.git). The git version can be browsed online.

I have written a wrapper script, port-up.sh, around the CRUX package tools and their configuration files /etc/pkgmk.conf and /etc/prt-get.conf that i find very comfortable, it reduces a full system update to

	# bin/port-up.sh -sU  # -s may not be available for you

	# # prt-get --test sysup
	# # bin/port-olay-check.sh
	# # .. olay adjustments, as necessary ..

	# bin/port-up.sh -d  # download anything
	# # no more web traffic

	# bin/port-up.sh -nq # build anything non-interactive + "quiet"
	# # in case of package errors fix that, build it via prt-get,
	# # and then call "# bin/port-up.sh -r" to resume normal flow

	# bin/port-trim.sh

Whereas port-up.sh is easily usable / adaptable (you surely want to adjust the BOX_PORTS variable), port-olay-check.sh and port-trim.sh are pretty much specific and depend on my style. In general it builds on directives in /etc/prt-get.conf:

	# two specific directories in order
	prtdir /usr/ports/olay-lock
	prtdir /usr/ports/olay
	# .. and whatever rest
	prtdir /usr/ports/stenur
	prtdir /usr/ports/core
	prtdir /usr/ports/opt
	prtdir /usr/ports/xorg
	prtdir /usr/ports/contrib

olay-lock and olay contain local overlays, ports in olay-lock are treated as if locked via prt-get lock PORT, whereas those in olay will be built as necessary, and automatically moved to olay-lock upon success To get reminded of possibly desired updates of overlayed ports run port-olay-check.sh.

Once an update was performed i call port-trim.sh, it looks for obsolete binaries (/usr/ports/built) and balls (/x/balls), and moves them to the respective .stale subdirectory, after cleaning whatever sits therein for over a week first. (For graceful functioning this requires git(1) based prtdirs: because the CRUX packet manager does not track which source files and upstream release tarballs etc. where used to create the prt-get current package, the installed version and the one represented by the Pkgfile in the portdir may have nothing in common -- but with git(1) the script can resolve the Pkgfile of the installed package, and therefore find and work on the proper files.) These two are mount points here, and in conjunction with file system snapshots i have a clean set of required source balls and built packages, with the recently replaced ones still available in .stale.