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
|
%global _empty_manifest_terminate_build 0
Name: python-noworkflow
Version: 1.12.0
Release: 1
Summary: Supporting infrastructure to run scientific experiments without a scientific workflow management system.
License: MIT
URL: https://github.com/gems-uff/noworkflow
Source0: https://mirrors.aliyun.com/pypi/web/packages/d2/31/1bde610e9620c399817d82a20e6e417d2002f3513431af006585e3ee4298/noworkflow-1.12.0.tar.gz
BuildArch: noarch
Requires: python3-pyposast
Requires: python3-apted
Requires: python3-future
Requires: python3-SQLAlchemy
Requires: python3-pyposast
Requires: python3-ipython
Requires: python3-jupyter
Requires: python3-flask
Requires: python3-pyswip-alt
Requires: python3-jsonpickle
Requires: python3-sphinx
Requires: python3-pyposast
Requires: python3-ipython
Requires: python3-jupyter
Requires: python3-sphinx
Requires: python3-pyposast
Requires: python3-flask
%description
Copyright (c) 2016 Universidade Federal Fluminense (UFF). Copyright (c)
2016 Polytechnic Institute of New York University. All rights reserved.
The noWorkflow project aims at allowing scientists to benefit from
provenance data analysis even when they don’t use a workflow system.
Also, the goal is to allow them to avoid using naming conventions to
store files originated in previous executions. Currently, when this is
not done, the result and intermediate files are overwritten by every new
execution of the pipeline.
noWorkflow was developed in Python and it currently is able to capture
provenance of Python scripts using Software Engineering techniques such
as abstract syntax tree (AST) analysis, reflection, and profiling, to
collect provenance without the need of a version control system or any
other environment.
Installing and using noWorkflow is simple and easy. Please check our
installation and basic usage guidelines below, and the `tutorial videos
at our Wiki
page <https://github.com/gems-uff/noworkflow/wiki/Videos>`__.
%package -n python3-noworkflow
Summary: Supporting infrastructure to run scientific experiments without a scientific workflow management system.
Provides: python-noworkflow
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-noworkflow
Copyright (c) 2016 Universidade Federal Fluminense (UFF). Copyright (c)
2016 Polytechnic Institute of New York University. All rights reserved.
The noWorkflow project aims at allowing scientists to benefit from
provenance data analysis even when they don’t use a workflow system.
Also, the goal is to allow them to avoid using naming conventions to
store files originated in previous executions. Currently, when this is
not done, the result and intermediate files are overwritten by every new
execution of the pipeline.
noWorkflow was developed in Python and it currently is able to capture
provenance of Python scripts using Software Engineering techniques such
as abstract syntax tree (AST) analysis, reflection, and profiling, to
collect provenance without the need of a version control system or any
other environment.
Installing and using noWorkflow is simple and easy. Please check our
installation and basic usage guidelines below, and the `tutorial videos
at our Wiki
page <https://github.com/gems-uff/noworkflow/wiki/Videos>`__.
%package help
Summary: Development documents and examples for noworkflow
Provides: python3-noworkflow-doc
%description help
Copyright (c) 2016 Universidade Federal Fluminense (UFF). Copyright (c)
2016 Polytechnic Institute of New York University. All rights reserved.
The noWorkflow project aims at allowing scientists to benefit from
provenance data analysis even when they don’t use a workflow system.
Also, the goal is to allow them to avoid using naming conventions to
store files originated in previous executions. Currently, when this is
not done, the result and intermediate files are overwritten by every new
execution of the pipeline.
noWorkflow was developed in Python and it currently is able to capture
provenance of Python scripts using Software Engineering techniques such
as abstract syntax tree (AST) analysis, reflection, and profiling, to
collect provenance without the need of a version control system or any
other environment.
Installing and using noWorkflow is simple and easy. Please check our
installation and basic usage guidelines below, and the `tutorial videos
at our Wiki
page <https://github.com/gems-uff/noworkflow/wiki/Videos>`__.
%prep
%autosetup -n noworkflow-1.12.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-noworkflow -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Thu Jun 08 2023 Python_Bot <Python_Bot@openeuler.org> - 1.12.0-1
- Package Spec generated
|
