"
hello
This issue is usually caused by a missing +MANIFEST file or explicitly declared packing list (pkg-plist/PLIST_FILES), leading to pkg thinking that a plain archive extraction is taking place instead of a proper transaction commit. When it fails to finalize the database commit, it will fail silently at the end of the extraction, leaving mess of .pkgtemp. files, not executing post-install scripts and refusing to create an entry in pkg.db. The proper way is to make sure that your Makefile lists all targets and files to be installed and utilizes standard ports macros (like those defined in SUB_FILES) to declare post-install phases instead of leaving some +POST_INSTALL.post lying around in your ports tree. You can check if your package actually contains the manifest by running pkg info -F my_package . pkg command.
This issue is usually caused by a missing +MANIFEST file or explicitly declared packing list (pkg-plist/PLIST_FILES), leading to pkg thinking that a plain archive extraction is taking place instead of a proper transaction commit. When it fails to finalize the database commit, it will fail silently at the end of the extraction, leaving mess of .pkgtemp. files, not executing post-install scripts and refusing to create an entry in pkg.db. The proper way is to make sure that your Makefile lists all targets and files to be installed and utilizes standard ports macros (like those defined in SUB_FILES) to declare post-install phases instead of leaving some +POST_INSTALL.post lying around in your ports tree. You can check if your package actually contains the manifest by running pkg info -F my_package . pkg command.
