summaryrefslogtreecommitdiff
path: root/python-dbispipeline.spec
blob: b2d18731c2db0cb17d0e6da93d70014b22d4fbeb (plain)
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
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
%global _empty_manifest_terminate_build 0
Name:		python-dbispipeline
Version:	0.8.30
Release:	1
Summary:	should make things more reproducible
License:	BSD License
URL:		https://git.uibk.ac.at/dbis/software/dbispipeline
Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/fd/fe/3a6aa98a849db50ac9a415b301a6132338c816c4149d545a20281d1a140a/dbispipeline-0.8.30.tar.gz
BuildArch:	noarch

Requires:	python3-gitpython
Requires:	python3-matplotlib
Requires:	python3-pandas
Requires:	python3-psycopg2-binary
Requires:	python3-scikit-learn
Requires:	python3-sqlalchemy
Requires:	python3-click
Requires:	python3-logzero
Requires:	python3-pyyaml

%description
    datasets:
      - music/acousticbrainz
      - music/billboard
      - music/millionsongdataset
    ```
    would assume that a physical directory exists at
    `/storage/nas3/datasets/music/billboard` and after calling the script
    `dbispipeline-link` without parameters using the above configuration, the
    following symlinks will be created:
    ```
    data/acousticbrainz -> /storage/nas3/datasets/music/acousticbrainz
    data/billboard -> /storage/nas3/datasets/music/billboard
    data/millionsongdataset -> /storage/nas3/datasets/music/millionsongdataset
    ```
    The value of `dataset_dir` from the config can be overwritten in the cli
    script by using the `-p` option.
## Requirements
* python >= 3.6
* a PostgreSQL database
* an email server if you want to use notification emails
## Installation
1. Install dbispipeline in your python. We recommend using pipenv to keep your
   dependencies clean: `pipenv install dbispipeline`
   This call will install a virtual environment as well as all dependencies.
2. Write your plan(s). See the example plan files for guidance.
3. call `pipenv run dp <yourplanfile.py>`
Enjoy!
## Configuration
The framework look in multiple directories for its configuration files.
* `/usr/local/etc/dbispipeline.ini` used for system wide default.
* `$HOME/.config/dbispipeline.ini` used for user specific configurations.
* `./dbispipeline.ini` for project specific configurations.
And example configuration file looks like this:
```ini
[database]
# url to your postgres database
host = your.personal.database
# your database user name
user = user
# port of your postgres database, default = 5432
# port = 5432
# password of your database user
password = <secure-password>
# database to use
database = pipelineresults
# table to be used
result_table = my_super_awesome_results
[project]
# this will be stored in the database
name = dbispipeline-test
# this is used to store backups of the execution
# it is possible to override this by setting the DBISPIPELINE_BACKUP_DIR
# environment variable
# the default is the temp dir of the os if this option is not set.
backup_dir = tmp
# this is used to linke the used datasets spcified in data/links.yaml
# it is possible to override this by setting the DBISPIPELINE_DATASET_DIR
# environment variable
dataset_dir = /storage/nas/datasets
[mail]
# email address to use as sender
sender = botname@yourserver.com
# recipient. This should probably be set on a home-directory-basis.
recipient = you@yourserver.com
# smtp server address to use
smtp_server = smtp.yourserver.com
# use smtp authentication, default = no
# authenticate = no
# username for smtp authentication, required if authenticate = yes
# username = foo
# password for smtp authentication, required if authenticate = yes
# password = bar
# port to use for smtp server connection, default = 465
# port = 465
```

%package -n python3-dbispipeline
Summary:	should make things more reproducible
Provides:	python-dbispipeline
BuildRequires:	python3-devel
BuildRequires:	python3-setuptools
BuildRequires:	python3-pip
%description -n python3-dbispipeline
    datasets:
      - music/acousticbrainz
      - music/billboard
      - music/millionsongdataset
    ```
    would assume that a physical directory exists at
    `/storage/nas3/datasets/music/billboard` and after calling the script
    `dbispipeline-link` without parameters using the above configuration, the
    following symlinks will be created:
    ```
    data/acousticbrainz -> /storage/nas3/datasets/music/acousticbrainz
    data/billboard -> /storage/nas3/datasets/music/billboard
    data/millionsongdataset -> /storage/nas3/datasets/music/millionsongdataset
    ```
    The value of `dataset_dir` from the config can be overwritten in the cli
    script by using the `-p` option.
## Requirements
* python >= 3.6
* a PostgreSQL database
* an email server if you want to use notification emails
## Installation
1. Install dbispipeline in your python. We recommend using pipenv to keep your
   dependencies clean: `pipenv install dbispipeline`
   This call will install a virtual environment as well as all dependencies.
2. Write your plan(s). See the example plan files for guidance.
3. call `pipenv run dp <yourplanfile.py>`
Enjoy!
## Configuration
The framework look in multiple directories for its configuration files.
* `/usr/local/etc/dbispipeline.ini` used for system wide default.
* `$HOME/.config/dbispipeline.ini` used for user specific configurations.
* `./dbispipeline.ini` for project specific configurations.
And example configuration file looks like this:
```ini
[database]
# url to your postgres database
host = your.personal.database
# your database user name
user = user
# port of your postgres database, default = 5432
# port = 5432
# password of your database user
password = <secure-password>
# database to use
database = pipelineresults
# table to be used
result_table = my_super_awesome_results
[project]
# this will be stored in the database
name = dbispipeline-test
# this is used to store backups of the execution
# it is possible to override this by setting the DBISPIPELINE_BACKUP_DIR
# environment variable
# the default is the temp dir of the os if this option is not set.
backup_dir = tmp
# this is used to linke the used datasets spcified in data/links.yaml
# it is possible to override this by setting the DBISPIPELINE_DATASET_DIR
# environment variable
dataset_dir = /storage/nas/datasets
[mail]
# email address to use as sender
sender = botname@yourserver.com
# recipient. This should probably be set on a home-directory-basis.
recipient = you@yourserver.com
# smtp server address to use
smtp_server = smtp.yourserver.com
# use smtp authentication, default = no
# authenticate = no
# username for smtp authentication, required if authenticate = yes
# username = foo
# password for smtp authentication, required if authenticate = yes
# password = bar
# port to use for smtp server connection, default = 465
# port = 465
```

%package help
Summary:	Development documents and examples for dbispipeline
Provides:	python3-dbispipeline-doc
%description help
    datasets:
      - music/acousticbrainz
      - music/billboard
      - music/millionsongdataset
    ```
    would assume that a physical directory exists at
    `/storage/nas3/datasets/music/billboard` and after calling the script
    `dbispipeline-link` without parameters using the above configuration, the
    following symlinks will be created:
    ```
    data/acousticbrainz -> /storage/nas3/datasets/music/acousticbrainz
    data/billboard -> /storage/nas3/datasets/music/billboard
    data/millionsongdataset -> /storage/nas3/datasets/music/millionsongdataset
    ```
    The value of `dataset_dir` from the config can be overwritten in the cli
    script by using the `-p` option.
## Requirements
* python >= 3.6
* a PostgreSQL database
* an email server if you want to use notification emails
## Installation
1. Install dbispipeline in your python. We recommend using pipenv to keep your
   dependencies clean: `pipenv install dbispipeline`
   This call will install a virtual environment as well as all dependencies.
2. Write your plan(s). See the example plan files for guidance.
3. call `pipenv run dp <yourplanfile.py>`
Enjoy!
## Configuration
The framework look in multiple directories for its configuration files.
* `/usr/local/etc/dbispipeline.ini` used for system wide default.
* `$HOME/.config/dbispipeline.ini` used for user specific configurations.
* `./dbispipeline.ini` for project specific configurations.
And example configuration file looks like this:
```ini
[database]
# url to your postgres database
host = your.personal.database
# your database user name
user = user
# port of your postgres database, default = 5432
# port = 5432
# password of your database user
password = <secure-password>
# database to use
database = pipelineresults
# table to be used
result_table = my_super_awesome_results
[project]
# this will be stored in the database
name = dbispipeline-test
# this is used to store backups of the execution
# it is possible to override this by setting the DBISPIPELINE_BACKUP_DIR
# environment variable
# the default is the temp dir of the os if this option is not set.
backup_dir = tmp
# this is used to linke the used datasets spcified in data/links.yaml
# it is possible to override this by setting the DBISPIPELINE_DATASET_DIR
# environment variable
dataset_dir = /storage/nas/datasets
[mail]
# email address to use as sender
sender = botname@yourserver.com
# recipient. This should probably be set on a home-directory-basis.
recipient = you@yourserver.com
# smtp server address to use
smtp_server = smtp.yourserver.com
# use smtp authentication, default = no
# authenticate = no
# username for smtp authentication, required if authenticate = yes
# username = foo
# password for smtp authentication, required if authenticate = yes
# password = bar
# port to use for smtp server connection, default = 465
# port = 465
```

%prep
%autosetup -n dbispipeline-0.8.30

%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-dbispipeline -f filelist.lst
%dir %{python3_sitelib}/*

%files help -f doclist.lst
%{_docdir}/*

%changelog
* Wed May 10 2023 Python_Bot <Python_Bot@openeuler.org> - 0.8.30-1
- Package Spec generated