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
|
%global _empty_manifest_terminate_build 0
Name: python-MakeItSo
Version: 0.6.1
Release: 1
Summary: filesystem template interpreter
License: MPL
URL: http://k0s.org/hg/MakeItSo
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/bd/72/e41e0cf1955340cd5689c394bd45d01980d1c814dd33efaf69d7bc2f8d0b/MakeItSo-0.6.1.tar.gz
BuildArch: noarch
%description
/templates for the people/
So people generally do things the easiest way possible. If you try to
get people to send you a file with, say, a "one-off" script, they will
probably hard code a bunch of stuff in it. Then, you're not really
sure what needs to be changed and because you're human you might make
a mistake. Worse, its a perl script and you're a python programmer.
You don't know what that script does!
And this is the time of the iceberg. If it really is a one-off, who
cares? But quickly one-offs become a deployment story, and not a very
efficient one.
%package -n python3-MakeItSo
Summary: filesystem template interpreter
Provides: python-MakeItSo
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-MakeItSo
/templates for the people/
So people generally do things the easiest way possible. If you try to
get people to send you a file with, say, a "one-off" script, they will
probably hard code a bunch of stuff in it. Then, you're not really
sure what needs to be changed and because you're human you might make
a mistake. Worse, its a perl script and you're a python programmer.
You don't know what that script does!
And this is the time of the iceberg. If it really is a one-off, who
cares? But quickly one-offs become a deployment story, and not a very
efficient one.
%package help
Summary: Development documents and examples for MakeItSo
Provides: python3-MakeItSo-doc
%description help
/templates for the people/
So people generally do things the easiest way possible. If you try to
get people to send you a file with, say, a "one-off" script, they will
probably hard code a bunch of stuff in it. Then, you're not really
sure what needs to be changed and because you're human you might make
a mistake. Worse, its a perl script and you're a python programmer.
You don't know what that script does!
And this is the time of the iceberg. If it really is a one-off, who
cares? But quickly one-offs become a deployment story, and not a very
efficient one.
%prep
%autosetup -n MakeItSo-0.6.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-MakeItSo -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Tue May 30 2023 Python_Bot <Python_Bot@openeuler.org> - 0.6.1-1
- Package Spec generated
|
