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
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
|
%global _empty_manifest_terminate_build 0
Name: python-autopip
Version: 1.6.0
Release: 1
Summary: Easily install apps from PyPI and automatically keep them updated
License: MIT
URL: https://github.com/maxzheng/autopip
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/24/95/d64f3fb2ab526cb7e9e81e4afc2b8a026b56174ee1050367770b6a76ea91/autopip-1.6.0.tar.gz
BuildArch: noarch
%description
Easily install apps from PyPI and automatically keep them updated.
`autopip` automates the creation of a virtual environment using `venv <https://docs.python.org/3/library/venv.html>`_ or
`virtualenv <https://virtualenv.pypa.io/>`_, installs any Python package with scripts (i.e. app) from PyPI using
`pip <https://pypi.org/project/pip/>`_, and atomically creates symlinks for installed scripts in `/usr/local/bin` so
you can easily use them. Each app version is installed cleanly into its own virtual environment. Optionally, it can
setup crontab entries to update apps automatically.
Before starting, check your Python installation -- while `autopip` can install Python apps that run on any Python
version, it requires Python 3.6+ to run::
curl -s https://raw.githubusercontent.com/maxzheng/autopip/master/etc/check-python.py | python
To install `autopip` to `/usr/local/bin`::
sudo pip3 install autopip
No need to worry about tainting system Python install as `autopip` has no install dependencies and never will.
Alternatively, you can install it in a virtual environment -- the last one that you will ever create manually for
installing Python apps::
python3.6 -m venv ~/.virtualenvs/autopip
source ~/.virtualenvs/autopip/bin/activate
pip3 install autopip
Optionally, create installation directories and chown to your user so that ``autopip`` can create symlinks in
`/usr/local/bin`::
sudo mkdir /usr/local/opt /usr/local/var
sudo chown -R $(whoami) /usr/local/*
Now, you can easily install any apps from PyPI:
$ autopip install workspace-tools --update daily
Installing workspace-tools to /usr/local/opt/apps/workspace-tools/3.2.2
Daily auto-update enabled via cron service
Updating symlinks in /usr/local/bin
+ wst
Install paths are selected based on your user's permission to write to `/opt` or `/usr/local/opt`. If you do not have
permission for either, then ``autopip`` will install apps to your user home at `~/.apps` with script symlinks in `~/bin`
therefore you will need to add `~/bin` to your PATH env var to easily run scripts from installed apps. To install
script symlinks to `/usr/local/bin`, either chown/chmod dirs in `/usr/local/*` to be writeable by your user as suggested
above or run ``autopip`` using ``sudo`` (i.e. as root). To see why a particular path is selected, append ``--debug``
after ``autopip`` when running it.
To save typing a few letters, you can also use the ``app`` alias -- short for **a**\ uto\ **p**\ i\ **p**.
$ app install ansible-hostmanager
Installing ansible-hostmanager to /usr/local/opt/apps/ansible-hostmanager/0.2.3
Updating script symlinks in /usr/local/bin
+ ah
To install an app for older or specific Python version, use the ``--python`` option:
$ app install ducktape --python 2.7
Installing ducktape to /usr/local/opt/apps/ducktape/0.7.3
Updating script symlinks in /usr/local/bin
+ ducktape
To show currently installed apps and their scripts:
$ app list --scripts
ansible-hostmanager 0.2.3 /usr/local/opt/apps/ansible-hostmanager/0.2.3
/usr/local/bin/ah
ducktape 0.7.3 /usr/local/opt/apps/ducktape/0.7.3
/usr/local/bin/ducktape
workspace-tools 3.2.2 /usr/local/opt/apps/workspace-tools/3.2.2 [updates daily]
/usr/local/bin/wst
To manually update all apps:
$ app update
ansible-hostmanager is up-to-date
ducktape is up-to-date
workspace-tools is up-to-date
To uninstall::
app uninstall ducktape
And you can even keep `autopip` updated automatically by installing itself:
$ app install autopip==1.* --update monthly
Installing autopip to /usr/local/opt/apps/autopip/1.0.0
Monthly auto-update enabled via cron service
Updating symlinks in /usr/local/bin
* app (updated)
* autopip (updated)
Now, that's convenience! ;)
If you need to use a private PyPI index, just configure `index-url` in `pip.conf
<https://pip.pypa.io/en/stable/user_guide/#configuration>`_ as `autopip` uses `pip` to install apps.
To control versioning and uniform installations across multiple hosts/users, you can also define an `autopip`
installation group using entry points. See example in `developer-tools <https://pypi.org/project/developer-tools/>`_
package.
%package -n python3-autopip
Summary: Easily install apps from PyPI and automatically keep them updated
Provides: python-autopip
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-autopip
Easily install apps from PyPI and automatically keep them updated.
`autopip` automates the creation of a virtual environment using `venv <https://docs.python.org/3/library/venv.html>`_ or
`virtualenv <https://virtualenv.pypa.io/>`_, installs any Python package with scripts (i.e. app) from PyPI using
`pip <https://pypi.org/project/pip/>`_, and atomically creates symlinks for installed scripts in `/usr/local/bin` so
you can easily use them. Each app version is installed cleanly into its own virtual environment. Optionally, it can
setup crontab entries to update apps automatically.
Before starting, check your Python installation -- while `autopip` can install Python apps that run on any Python
version, it requires Python 3.6+ to run::
curl -s https://raw.githubusercontent.com/maxzheng/autopip/master/etc/check-python.py | python
To install `autopip` to `/usr/local/bin`::
sudo pip3 install autopip
No need to worry about tainting system Python install as `autopip` has no install dependencies and never will.
Alternatively, you can install it in a virtual environment -- the last one that you will ever create manually for
installing Python apps::
python3.6 -m venv ~/.virtualenvs/autopip
source ~/.virtualenvs/autopip/bin/activate
pip3 install autopip
Optionally, create installation directories and chown to your user so that ``autopip`` can create symlinks in
`/usr/local/bin`::
sudo mkdir /usr/local/opt /usr/local/var
sudo chown -R $(whoami) /usr/local/*
Now, you can easily install any apps from PyPI:
$ autopip install workspace-tools --update daily
Installing workspace-tools to /usr/local/opt/apps/workspace-tools/3.2.2
Daily auto-update enabled via cron service
Updating symlinks in /usr/local/bin
+ wst
Install paths are selected based on your user's permission to write to `/opt` or `/usr/local/opt`. If you do not have
permission for either, then ``autopip`` will install apps to your user home at `~/.apps` with script symlinks in `~/bin`
therefore you will need to add `~/bin` to your PATH env var to easily run scripts from installed apps. To install
script symlinks to `/usr/local/bin`, either chown/chmod dirs in `/usr/local/*` to be writeable by your user as suggested
above or run ``autopip`` using ``sudo`` (i.e. as root). To see why a particular path is selected, append ``--debug``
after ``autopip`` when running it.
To save typing a few letters, you can also use the ``app`` alias -- short for **a**\ uto\ **p**\ i\ **p**.
$ app install ansible-hostmanager
Installing ansible-hostmanager to /usr/local/opt/apps/ansible-hostmanager/0.2.3
Updating script symlinks in /usr/local/bin
+ ah
To install an app for older or specific Python version, use the ``--python`` option:
$ app install ducktape --python 2.7
Installing ducktape to /usr/local/opt/apps/ducktape/0.7.3
Updating script symlinks in /usr/local/bin
+ ducktape
To show currently installed apps and their scripts:
$ app list --scripts
ansible-hostmanager 0.2.3 /usr/local/opt/apps/ansible-hostmanager/0.2.3
/usr/local/bin/ah
ducktape 0.7.3 /usr/local/opt/apps/ducktape/0.7.3
/usr/local/bin/ducktape
workspace-tools 3.2.2 /usr/local/opt/apps/workspace-tools/3.2.2 [updates daily]
/usr/local/bin/wst
To manually update all apps:
$ app update
ansible-hostmanager is up-to-date
ducktape is up-to-date
workspace-tools is up-to-date
To uninstall::
app uninstall ducktape
And you can even keep `autopip` updated automatically by installing itself:
$ app install autopip==1.* --update monthly
Installing autopip to /usr/local/opt/apps/autopip/1.0.0
Monthly auto-update enabled via cron service
Updating symlinks in /usr/local/bin
* app (updated)
* autopip (updated)
Now, that's convenience! ;)
If you need to use a private PyPI index, just configure `index-url` in `pip.conf
<https://pip.pypa.io/en/stable/user_guide/#configuration>`_ as `autopip` uses `pip` to install apps.
To control versioning and uniform installations across multiple hosts/users, you can also define an `autopip`
installation group using entry points. See example in `developer-tools <https://pypi.org/project/developer-tools/>`_
package.
%package help
Summary: Development documents and examples for autopip
Provides: python3-autopip-doc
%description help
Easily install apps from PyPI and automatically keep them updated.
`autopip` automates the creation of a virtual environment using `venv <https://docs.python.org/3/library/venv.html>`_ or
`virtualenv <https://virtualenv.pypa.io/>`_, installs any Python package with scripts (i.e. app) from PyPI using
`pip <https://pypi.org/project/pip/>`_, and atomically creates symlinks for installed scripts in `/usr/local/bin` so
you can easily use them. Each app version is installed cleanly into its own virtual environment. Optionally, it can
setup crontab entries to update apps automatically.
Before starting, check your Python installation -- while `autopip` can install Python apps that run on any Python
version, it requires Python 3.6+ to run::
curl -s https://raw.githubusercontent.com/maxzheng/autopip/master/etc/check-python.py | python
To install `autopip` to `/usr/local/bin`::
sudo pip3 install autopip
No need to worry about tainting system Python install as `autopip` has no install dependencies and never will.
Alternatively, you can install it in a virtual environment -- the last one that you will ever create manually for
installing Python apps::
python3.6 -m venv ~/.virtualenvs/autopip
source ~/.virtualenvs/autopip/bin/activate
pip3 install autopip
Optionally, create installation directories and chown to your user so that ``autopip`` can create symlinks in
`/usr/local/bin`::
sudo mkdir /usr/local/opt /usr/local/var
sudo chown -R $(whoami) /usr/local/*
Now, you can easily install any apps from PyPI:
$ autopip install workspace-tools --update daily
Installing workspace-tools to /usr/local/opt/apps/workspace-tools/3.2.2
Daily auto-update enabled via cron service
Updating symlinks in /usr/local/bin
+ wst
Install paths are selected based on your user's permission to write to `/opt` or `/usr/local/opt`. If you do not have
permission for either, then ``autopip`` will install apps to your user home at `~/.apps` with script symlinks in `~/bin`
therefore you will need to add `~/bin` to your PATH env var to easily run scripts from installed apps. To install
script symlinks to `/usr/local/bin`, either chown/chmod dirs in `/usr/local/*` to be writeable by your user as suggested
above or run ``autopip`` using ``sudo`` (i.e. as root). To see why a particular path is selected, append ``--debug``
after ``autopip`` when running it.
To save typing a few letters, you can also use the ``app`` alias -- short for **a**\ uto\ **p**\ i\ **p**.
$ app install ansible-hostmanager
Installing ansible-hostmanager to /usr/local/opt/apps/ansible-hostmanager/0.2.3
Updating script symlinks in /usr/local/bin
+ ah
To install an app for older or specific Python version, use the ``--python`` option:
$ app install ducktape --python 2.7
Installing ducktape to /usr/local/opt/apps/ducktape/0.7.3
Updating script symlinks in /usr/local/bin
+ ducktape
To show currently installed apps and their scripts:
$ app list --scripts
ansible-hostmanager 0.2.3 /usr/local/opt/apps/ansible-hostmanager/0.2.3
/usr/local/bin/ah
ducktape 0.7.3 /usr/local/opt/apps/ducktape/0.7.3
/usr/local/bin/ducktape
workspace-tools 3.2.2 /usr/local/opt/apps/workspace-tools/3.2.2 [updates daily]
/usr/local/bin/wst
To manually update all apps:
$ app update
ansible-hostmanager is up-to-date
ducktape is up-to-date
workspace-tools is up-to-date
To uninstall::
app uninstall ducktape
And you can even keep `autopip` updated automatically by installing itself:
$ app install autopip==1.* --update monthly
Installing autopip to /usr/local/opt/apps/autopip/1.0.0
Monthly auto-update enabled via cron service
Updating symlinks in /usr/local/bin
* app (updated)
* autopip (updated)
Now, that's convenience! ;)
If you need to use a private PyPI index, just configure `index-url` in `pip.conf
<https://pip.pypa.io/en/stable/user_guide/#configuration>`_ as `autopip` uses `pip` to install apps.
To control versioning and uniform installations across multiple hosts/users, you can also define an `autopip`
installation group using entry points. See example in `developer-tools <https://pypi.org/project/developer-tools/>`_
package.
%prep
%autosetup -n autopip-1.6.0
%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-autopip -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 1.6.0-1
- Package Spec generated
|
