Not sure if this is intended or not - it certainly wasn't the case with 12.2, and it likely will break a few automated deploys:
# ls -la pkg* -rw-r--r-- 1 root wheel 4011616 Nov 17 17:52 pkg-1.17.2.pkg # pkg add /tmp/vb/pkg-1.17.2.pkg < /dev/null The package management tool is not yet installed on your system. Please set ASSUME_ALWAYS_YES=yes environment variable [etc.etc.] Okay, lets try that one: # pkg add -y /tmp/vb/pkg-1.17.2.pkg < /dev/null Bootstrapping pkg from https://oper-e.intra.daemon.contact/sysimg/ports/conr/Cur, please wait... pkg: Error fetching https://oper-e.intra.daemon.contact/sysimg/ports/conr/Cur/Latest/pkg.txz: Not Found A pre-built version of pkg could not be found for your system. Consider changing PACKAGESITE or installing it from ports: 'ports-mgmt/pkg'. Not good. Not at all. But then: # pwd /tmp/vb # pkg add pkg-1.17.2.pkg < /dev/null Installing pkg-1.17.2... Extracting pkg-1.17.2: 100% So, it *can* still do it. It just does no longer accept an (absolute or relative) pathname. And I have no idea what that might be good for. Any clues, anybody? cheerio, PMc
