1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
|
%global _empty_manifest_terminate_build 0
Name: python-patchwork
Version: 1.0.1
Release: 1
Summary: Deployment/sysadmin operations, powered by Fabric
License: BSD
URL: https://fabric-patchwork.readthedocs.io
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/8d/0f/df3d4d1846dc0b6d06e94c77709352bc867212d0caed1255c51bab6d5c2b/patchwork-1.0.1.tar.gz
BuildArch: noarch
Requires: python3-fabric
%description
Patchwork is a mid-level library of Unix system administration primitives such
as "install package" or "create user account", interrogative functionality for
introspecting system state, and other commonly useful functions built on top of
the `Fabric <http://fabfile.org>`_ library.
Specifically:
- Primary API calls strive to be **idempotent**: they may be called multiple
times in a row without unwanted changes piling up or causing errors.
- Patchwork **is just an API**: it has no concept of "recipes", "manifests",
"classes", "roles" or other high level organizational units. This is left up
to the user or wrapping libraries.
- This is one way Patchwork differs from larger configuration management
frameworks like `Chef <http://opscode.com/chef/>`_ or `Puppet
<http://puppetlabs.com>`_. Patchwork is closest in nature to those tools'
"resources."
- It is implemented in **shell calls**, typically sent **over SSH** from a
local workstation.
- However, where possible, its functions expect a baseline Invoke
`~invoke.context.Context` object and can thus run locally *or* remotely,
depending on the specific context supplied by the caller.
%package -n python3-patchwork
Summary: Deployment/sysadmin operations, powered by Fabric
Provides: python-patchwork
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-patchwork
Patchwork is a mid-level library of Unix system administration primitives such
as "install package" or "create user account", interrogative functionality for
introspecting system state, and other commonly useful functions built on top of
the `Fabric <http://fabfile.org>`_ library.
Specifically:
- Primary API calls strive to be **idempotent**: they may be called multiple
times in a row without unwanted changes piling up or causing errors.
- Patchwork **is just an API**: it has no concept of "recipes", "manifests",
"classes", "roles" or other high level organizational units. This is left up
to the user or wrapping libraries.
- This is one way Patchwork differs from larger configuration management
frameworks like `Chef <http://opscode.com/chef/>`_ or `Puppet
<http://puppetlabs.com>`_. Patchwork is closest in nature to those tools'
"resources."
- It is implemented in **shell calls**, typically sent **over SSH** from a
local workstation.
- However, where possible, its functions expect a baseline Invoke
`~invoke.context.Context` object and can thus run locally *or* remotely,
depending on the specific context supplied by the caller.
%package help
Summary: Development documents and examples for patchwork
Provides: python3-patchwork-doc
%description help
Patchwork is a mid-level library of Unix system administration primitives such
as "install package" or "create user account", interrogative functionality for
introspecting system state, and other commonly useful functions built on top of
the `Fabric <http://fabfile.org>`_ library.
Specifically:
- Primary API calls strive to be **idempotent**: they may be called multiple
times in a row without unwanted changes piling up or causing errors.
- Patchwork **is just an API**: it has no concept of "recipes", "manifests",
"classes", "roles" or other high level organizational units. This is left up
to the user or wrapping libraries.
- This is one way Patchwork differs from larger configuration management
frameworks like `Chef <http://opscode.com/chef/>`_ or `Puppet
<http://puppetlabs.com>`_. Patchwork is closest in nature to those tools'
"resources."
- It is implemented in **shell calls**, typically sent **over SSH** from a
local workstation.
- However, where possible, its functions expect a baseline Invoke
`~invoke.context.Context` object and can thus run locally *or* remotely,
depending on the specific context supplied by the caller.
%prep
%autosetup -n patchwork-1.0.1
%build
%py3_build
%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .
%files -n python3-patchwork -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Wed Apr 12 2023 Python_Bot <Python_Bot@openeuler.org> - 1.0.1-1
- Package Spec generated
|
