From: Konrad Lipinski <k.lipinski2@partner.samsung.com>
Date: Tue, 28 May 2019 16:04:01 +0000 (+0200)
Subject: Make spec compliant with gbs --incremental
X-Git-Tag: submit/tizen/20190704.112637~1
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=f25b59b9c7b91548e306e3237b9bd58902622fee;p=platform%2Fcore%2Fsecurity%2Flibcryptsvc.git

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
---

diff --git a/packaging/libcryptsvc.spec b/packaging/libcryptsvc.spec
index e27b0b5..55059e1 100644
--- a/packaging/libcryptsvc.spec
+++ b/packaging/libcryptsvc.spec
@@ -35,7 +35,6 @@ Testing for Crypto Service.
 
 %prep
 %setup -q
-cp %{SOURCE1001} .
 
 %build
 export CFLAGS="$CFLAGS -DTIZEN_DEBUG_ENABLE"
@@ -68,6 +67,8 @@ make %{?jobs:-j%jobs}
 
 %install
 %make_install
+mkdir -p %{buildroot}%{_datadir}/
+cp -a %{SOURCE1001} %{buildroot}%{_datadir}/
 
 
 %post -p /sbin/ldconfig
@@ -75,7 +76,7 @@ make %{?jobs:-j%jobs}
 %postun -p /sbin/ldconfig
 
 %files
-%manifest %{name}.manifest
+%manifest %{_datadir}/%{name}.manifest
 %license LICENSE
 %license LICENSE.BSL-1.0
 %{_libdir}/libcryptsvc.so.*