summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKonrad Lipinski <k.lipinski2@partner.samsung.com>2019-05-28 16:23:42 +0200
committerKonrad Lipinski <k.lipinski2@partner.samsung.com>2019-05-28 16:24:31 +0200
commit2b6cb70e628fe58b679f7cd80bbd3cc6a0546495 (patch)
tree9e6277a9ca359b676838610e4b8fe0a87e72792c
parent00769aaa1dff561d36976480ad6df75a7e2567a6 (diff)
downloadca-certificates-tizen-2b6cb70e628fe58b679f7cd80bbd3cc6a0546495.tar.gz
ca-certificates-tizen-2b6cb70e628fe58b679f7cd80bbd3cc6a0546495.tar.bz2
ca-certificates-tizen-2b6cb70e628fe58b679f7cd80bbd3cc6a0546495.zip
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: I8dfbf5399364333880fcb63ba8e4163a32994312
-rw-r--r--packaging/ca-certificates-tizen.spec4
1 files changed, 2 insertions, 2 deletions
diff --git a/packaging/ca-certificates-tizen.spec b/packaging/ca-certificates-tizen.spec
index 93ebb4d..209122a 100644
--- a/packaging/ca-certificates-tizen.spec
+++ b/packaging/ca-certificates-tizen.spec
@@ -34,7 +34,6 @@ Requires: %name = %version-%release
%prep
%setup -q
-cp %{SOURCE1001} .
%build
@@ -68,10 +67,11 @@ mkdir -p %{buildroot}%{ro_etc_dir}/rpm
touch %{buildroot}%{macro_ca_certificates_tizen}
echo "%TZ_SYS_REVOKED_CERTS_FINGERPRINTS_RUNTIME %{fingerprint_rw_dir}/fingerprint_list_runtime.xml" >> %{buildroot}%{macro_ca_certificates_tizen}
+cp %{SOURCE1001} %{buildroot}%{_datadir}/
%files
%defattr(-,root,root,-)
-%manifest %{name}.manifest
+%manifest %{_datadir}/%{name}.manifest
%license LICENSE
%{tizen_dir}/*
%{fingerprint_dir}/*