Make spec compliant with gbs --incremental 02/206902/1
authorKonrad Lipinski <k.lipinski2@partner.samsung.com>
Tue, 28 May 2019 16:04:01 +0000 (18:04 +0200)
committerKonrad Lipinski <k.lipinski2@partner.samsung.com>
Tue, 28 May 2019 16:05:00 +0000 (18:05 +0200)
commitf25b59b9c7b91548e306e3237b9bd58902622fee
tree7e84f085ef440113c48b7c109f007305a65b0294
parent60698e1acfbc700957c2bf5000c522b67d7fd3b2
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.

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: I96a6e3fcd8a0f1fdf16121e7d2ef77603200739b
packaging/libcryptsvc.spec