diff options
| author | Konrad Lipinski <k.lipinski2@partner.samsung.com> | 2019-05-28 18:04:01 +0200 |
|---|---|---|
| committer | Konrad Lipinski <k.lipinski2@partner.samsung.com> | 2019-05-28 18:05:00 +0200 |
| commit | f25b59b9c7b91548e306e3237b9bd58902622fee (patch) | |
| tree | 7e84f085ef440113c48b7c109f007305a65b0294 | |
| parent | 60698e1acfbc700957c2bf5000c522b67d7fd3b2 (diff) | |
| download | libcryptsvc-f25b59b9c7b91548e306e3237b9bd58902622fee.tar.gz libcryptsvc-f25b59b9c7b91548e306e3237b9bd58902622fee.tar.bz2 libcryptsvc-f25b59b9c7b91548e306e3237b9bd58902622fee.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: I96a6e3fcd8a0f1fdf16121e7d2ef77603200739b
| -rw-r--r-- | packaging/libcryptsvc.spec | 5 |
1 files changed, 3 insertions, 2 deletions
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.* |