1. for centos, use @SYSCONFDIR@ to represent %{_sysconfdir} which
is determined in spec file and could be different in different Linux.
2. use @PYTHONROOT@ to represent the actual %{pythonroot} which is
determined in spec file or other packaging file. For example, for
python2.7, %{pythonroot} could be "/usr/lib64/python2.7/site-packages"
or "/usr/lib64/python3.x/site-packages" for python3.x respectively.
3. test method:
1). run "build-pkgs" and "build-iso", and then check src RPM
"nfv-1.0-75.tis.src.rpm" in which related scripts are correctly set
with @SYSCONFDIR@ and @PYTHONROOT@. Also check CentOS binary RPM
"nfv-vim-1.0-75.tis.x86_64.rpm" to assure @SYSCONFDIR@ is correctly
replaced by "/etc" for CentOS and "@PYTHON@" is actually updated to
"/usr/lib64/python2.7/site-packages/" for python2.7.
2). use the newly built iso, install StarlingX system on virtual or
bare metal, and check basic functionalities.
Story: 2004039
Task: 27043
Depends-On: https://review.openstack.org/#/c/611725/
Change-Id: Ie6e05d24a476fe2977f1003d23f747f5a0b779a3
Signed-off-by: Yong Hu <yong.hu@intel.com>
45dfb5417c