directive to provided file by RPM but keep file after RPM uninstallation?

[realsobek]

Hi,

is there an RPM directive that tells RPM to leave a file in place (even if it is unchanged), when the RPM that provided the file is uninstalled? I want to use it for distribution of a custom support script (setup and introduction of/for new users in their session) with RPM (no configuration management system present). I searched for a SPEC directive no avail:
http://ftp.rpm.org/max-rpm/s1-rpm-inside-files-list-directives.html
https://rpm-software-management.github.io/rpm/manual/spec.html
https://docs.fedoraproject.org/en-US/packaging-guidelines/AutoProvidesAndRequiresFiltering/
config and ghost were the best I could find, but they do not match my requirements.

I am inexperienced with creation of RPM files. I got it to work with a custom SPEC file, RPM package that:

• defines "%global FILE4 /usr/local/NAME.bash" below the SPEC header
• uses %{FILE4}.temp:

  %install
  mkdir -p %{buildroot}/usr/local
  install -m 0755 /.../NAME.bash %{buildroot}%{FILE4}.temp
  
  %files
  %{FILE4}.temp
  

• in "%post -p /bin/bash" section runs:

  if [[ "%{FILE4}.temp" -nt "%{FILE4}" ]]; then
     mv "%{FILE4}.temp" "%{FILE4}"
  fi
  

  to write only on updates, and make sure the file remains in place even when the RPM is uninstalled.

It is OK if you say this does not exist and will not be implemented. Thank you for your input. :)
Would this be better served with a configuration management system (Ansible, ...)? For on-site and off-site clients?