Packages created by 3rd party SlackBuild scripts fail to install properly on -current
by Ser Olmy from LinuxQuestions.org on (#5ACPA)
I just tried to build and install a few SBo packages on -current, but I've run into a peculiar issue.
The problem occurs with packages where the number of config files have to be determined at build time. For instance, the SlackBuild script script for strongSwan handles this by creating a file called conffiles with a list of file names, and then has code in doinst.sh reference this file.
When I install the resulting package on a fresh install of Slackware-current (downloaded today, 2020-11-14), this happens:Code:Executing install script for strongswan-5.9.1-x86_64-1_SBo.tgz.
cat: install/conffiles: No such file or directory
Package strongswan-5.9.1-x86_64-1_SBo.tgz installed.
~#Adding debug statements to doinst.sh reveals that the working directory appears to be / (root), rather than the temporary directory in which the package was extracted ( which is what the script expects).
Also, whenever I run installpkg, a subdirectory called "installpkg-<long random hex number>" is created in the root directory.
Is this a bug in the SlackBuild script? Or am I missing something obvious here?
The problem occurs with packages where the number of config files have to be determined at build time. For instance, the SlackBuild script script for strongSwan handles this by creating a file called conffiles with a list of file names, and then has code in doinst.sh reference this file.
When I install the resulting package on a fresh install of Slackware-current (downloaded today, 2020-11-14), this happens:Code:Executing install script for strongswan-5.9.1-x86_64-1_SBo.tgz.
cat: install/conffiles: No such file or directory
Package strongswan-5.9.1-x86_64-1_SBo.tgz installed.
~#Adding debug statements to doinst.sh reveals that the working directory appears to be / (root), rather than the temporary directory in which the package was extracted ( which is what the script expects).
Also, whenever I run installpkg, a subdirectory called "installpkg-<long random hex number>" is created in the root directory.
Is this a bug in the SlackBuild script? Or am I missing something obvious here?