Hello, I am in the process of upgrading some proprietary software that has always been deployed via a "custom" package created by the old pkg_create. So far I've been able to use "pkg create" to achieve what I want, but it seems that the "requirements" script is no longer a part of the new pkg framework. This used to be a script that you could include with a package that could halt the pkg add or remove process by returning a non-zero exit code from the script. I've been using it with the old pkg tools as a way to enforce some proprietary requirements logic that goes beyond requiring certain pkg dependencies, architecture, etc. One example is to make sure a specific custom kernel is running by analyzing uname output.
I am wondering if anyone has a suggestion as to how to interrupt the pkg add process in a similar way. It looks like the "requirements" script has been removed entirely, and from what I can tell a failure in the pre-install script does not halt pkg add. Thanks. -Nick _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[email protected]"
