Merge "split userdata-backup pkg from factory-reset" into tizen_4.0submit/tizen_4.0/20171213.213624accepted/tizen/4.0/unified/20171220.064247

1 files changed, 16 insertions, 1 deletions

diff --git a/packaging/factory-reset.spec b/packaging/factory-reset.spec
index 0662111..60e2eb9 100755
--- a/packaging/factory-reset.spec
+++ b/packaging/factory-reset.spec
@@ -36,6 +36,14 @@ preconfiguration
 It would be not only called by testers after many kind of verification tests
 but it also be called by Manufacture Steps for all products.
 
+%package userdata-backup
+Summary:    Vconf internal keys (devel)
+Group:      Application Framework/Configuration
+
+
+%description userdata-backup
+userdata-backup make a backup data for user r/w data area by archieving with tar/zip.
+
 %prep
 %setup -q
 
@@ -84,7 +92,10 @@ install -m 0644 %SOURCE3 %{buildroot}%{_datadir}/dbus-1/system-services/org.tize
 %{_libdir}/systemd/system/multi-user.target.wants/factory-reset.service
 %license LICENSE
 /etc/smack/accesses2.d/%{name}.rule
-%attr(700,root,root) %{_bindir}/*.sh
+%attr(700,root,root) %{_bindir}/factoryreset-verify-result.sh*
+%attr(700,root,root) %{_bindir}/factoryreset-verify.sh
+%attr(700,root,root) %{_bindir}/run-factory-reset.sh*
+
 %attr(755,root,root) %{_bindir}/rstsmack
 %attr(744,root,root) %{_bindir}/factory-reset
 %{_datadir}/dbus-1/system-services/org.tizen.factory-reset.service
@@ -94,3 +105,7 @@ install -m 0644 %SOURCE3 %{buildroot}%{_datadir}/dbus-1/system-services/org.tize
 %if 0%{?sec_product_feature_security_mdfpp_enable}
 %attr(700,root,root) %{_bindir}/resetCCMode
 %endif
+
+%files userdata-backup
+%license LICENSE
+%attr(700,root,root) %{_bindir}/build-backup-data.sh*