CRAN came knocking because our package is one of the remaining ones (the other is, <cough, cough> mine too ...) requiring to set StagedInstall: no in DESCRIPTION. This goes way back to when @jeroen helped us get to the package CRAN-ready and has to do with the fact that we (at the time) opted for absolute paths via @rpath instructions to the dynamic linker.
Well turns out relative ones work too, and @kalibera was of excellent assistance here so this now works. I also sent it to RHub's macOS test instance (that use the CRAN setup, not the one using brew) and it passed too. This needed changes to no longer Suggests: on the now-departed fts package, I will send those in subsequent PR.
CRAN came knocking because our package is one of the remaining ones (the other is, <cough, cough> mine too ...) requiring to set
StagedInstall: no
inDESCRIPTION
. This goes way back to when @jeroen helped us get to the package CRAN-ready and has to do with the fact that we (at the time) opted for absolute paths via@rpath
instructions to the dynamic linker.Well turns out relative ones work too, and @kalibera was of excellent assistance here so this now works. I also sent it to RHub's macOS test instance (that use the CRAN setup, not the one using
brew
) and it passed too. This needed changes to no longerSuggests:
on the now-departedfts
package, I will send those in subsequent PR.