Make spec compliant with gbs --incremental 51/183551/1
authorKonrad Lipinski <k.lipinski2@partner.samsung.com>
Fri, 6 Jul 2018 10:39:14 +0000 (12:39 +0200)
committerKonrad Lipinski <k.lipinski2@partner.samsung.com>
Fri, 6 Jul 2018 10:50:36 +0000 (12:50 +0200)
commite1bfaa916ea326b5826b1ae1ea24eb6232ff67a9
tree08fb8e5d73a7806792ed6dbd230071e4680de3c0
parent23b4001ac4e9ba85fc350b9cdfd7fd0a2fb9826d
Make spec compliant with gbs --incremental

According to [1], %prep section of the spec file should contain a single
%setup macro, nothing else. According to [2], manifest files are best
copied to %{buildroot}%{_datadir} in the %install section.

Moved manifest copy operations from %prep to %install accordingly.

As a byproduct, got a warning about an installed but unpackaged file:
  security-manager-tests.manifest
Corrected the '%files -n security-manager-tests' accordingly by spelling
out the file name verbatim.

References
[1] https://source.tizen.org/documentation/reference/git-build-system/usage/gbs-build
[2] https://wiki.tizen.org/Security/Application_installation_and_Manifest

Change-Id: I29beaccfc83ae65698833696497c0f8791651ffc
packaging/security-manager.spec