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
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
|
%global _empty_manifest_terminate_build 0
Name: python-hgdistver
Version: 0.25
Release: 1
Summary: obsoleted by setuptools_scm
License: MIT
URL: http://bitbucket.org/RonnyPfannschmidt/hgdistver/
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/98/7b/337f0108b7d2236a6c76eadfd457815fb91b0aa637e43c22947fa7f4050c/hgdistver-0.25.tar.gz
BuildArch: noarch
%description
hgdistver
~~~~~~~~~
.. warning::
this module is superseeded by setuptools_scm
This module is a simple drop-in to support setup.py
in mercurial and git based projects.
Alternatively it can be a setup time requirement.
It extracts the last Tag as well as the distance to it in commits
from the scm, and uses these to calculate a version number
By default, it will increment the last component of the Version by one
and append .dev{distance}
in case the last component is .dev, the version will be unchanged
Tis requires always using all components in tags (i.e. 2.0.0 instead of 2.0)
to avoid misstakenly releasing higher version
(i.e. 2.1.devX instead of 2.0.1.devX)
It uses 4 strategies to archive its task:
1. try to directly ask hg for the tag/distance
2. try to infer it from the `.hg_archival.txt` file
3. try to read the exact version the cache file if it exists
4. try to read the exact version from the 'PKG-INFO' file
as generated by `setup.py sdists` (this is a nasty abuse)
The most simple usage is::
from setuptools import setup
from hgdistver import get_version
setup(
...,
version=get_version(),
...,
)
`get_version` takes the optional argument `cachefile`,
which causes it to store the version info in a python script instead
of abusing PKG-INFO from a sdist.
The setup requirement usage is::
from setuptools import setup
setup(
...,
get_version_from_hg=True,
setup_requires=['hgdistver'],
...,
)
The requirement uses the setup argument cache_hg_version_to instead of cachefile.
%package -n python3-hgdistver
Summary: obsoleted by setuptools_scm
Provides: python-hgdistver
BuildRequires: python3-devel
BuildRequires: python3-setuptools
%description -n python3-hgdistver
hgdistver
~~~~~~~~~
.. warning::
this module is superseeded by setuptools_scm
This module is a simple drop-in to support setup.py
in mercurial and git based projects.
Alternatively it can be a setup time requirement.
It extracts the last Tag as well as the distance to it in commits
from the scm, and uses these to calculate a version number
By default, it will increment the last component of the Version by one
and append .dev{distance}
in case the last component is .dev, the version will be unchanged
Tis requires always using all components in tags (i.e. 2.0.0 instead of 2.0)
to avoid misstakenly releasing higher version
(i.e. 2.1.devX instead of 2.0.1.devX)
It uses 4 strategies to archive its task:
1. try to directly ask hg for the tag/distance
2. try to infer it from the `.hg_archival.txt` file
3. try to read the exact version the cache file if it exists
4. try to read the exact version from the 'PKG-INFO' file
as generated by `setup.py sdists` (this is a nasty abuse)
The most simple usage is::
from setuptools import setup
from hgdistver import get_version
setup(
...,
version=get_version(),
...,
)
`get_version` takes the optional argument `cachefile`,
which causes it to store the version info in a python script instead
of abusing PKG-INFO from a sdist.
The setup requirement usage is::
from setuptools import setup
setup(
...,
get_version_from_hg=True,
setup_requires=['hgdistver'],
...,
)
The requirement uses the setup argument cache_hg_version_to instead of cachefile.
%package help
Summary: Development documents and examples for hgdistver
Provides: python3-hgdistver-doc
%description help
hgdistver
~~~~~~~~~
.. warning::
this module is superseeded by setuptools_scm
This module is a simple drop-in to support setup.py
in mercurial and git based projects.
Alternatively it can be a setup time requirement.
It extracts the last Tag as well as the distance to it in commits
from the scm, and uses these to calculate a version number
By default, it will increment the last component of the Version by one
and append .dev{distance}
in case the last component is .dev, the version will be unchanged
Tis requires always using all components in tags (i.e. 2.0.0 instead of 2.0)
to avoid misstakenly releasing higher version
(i.e. 2.1.devX instead of 2.0.1.devX)
It uses 4 strategies to archive its task:
1. try to directly ask hg for the tag/distance
2. try to infer it from the `.hg_archival.txt` file
3. try to read the exact version the cache file if it exists
4. try to read the exact version from the 'PKG-INFO' file
as generated by `setup.py sdists` (this is a nasty abuse)
The most simple usage is::
from setuptools import setup
from hgdistver import get_version
setup(
...,
version=get_version(),
...,
)
`get_version` takes the optional argument `cachefile`,
which causes it to store the version info in a python script instead
of abusing PKG-INFO from a sdist.
The setup requirement usage is::
from setuptools import setup
setup(
...,
get_version_from_hg=True,
setup_requires=['hgdistver'],
...,
)
The requirement uses the setup argument cache_hg_version_to instead of cachefile.
%prep
%autosetup -n hgdistver-0.25
%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-hgdistver -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Sat Feb 25 2023 Python_Bot <Python_Bot@openeuler.org> - 0.25-1
- Package Spec generated
|
