automatic import of python-apachedex

1 files changed, 135 insertions, 0 deletions

diff --git a/python-apachedex.spec b/python-apachedex.spec
new file mode 100644
index 0000000..04b742d
--- /dev/null
+++ b/python-apachedex.spec
@@ -0,0 +1,135 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-APacheDEX
+Version:	1.8
+Release:	1
+Summary:	Compute APDEX from Apache-style logs.
+License:	GPL 2+
+URL:		http://git.erp5.org/gitweb/apachedex.git
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/9e/3c/63e6fbcea81746ae437a58406ed06b8e05afe4a50219c568ca9607fcded1/APacheDEX-1.8.tar.gz
+BuildArch:	noarch
+
+
+%description
+Parses Apache-style logs and generates several statistics intended for a
+website developer audience:
+- APDEX (Application Performance inDEX, see http://www.apdex.org) ratio
+  (plotted)
+  Because you want to know how satisfied your users are.
+- hit count (plotted)
+  Because achieving 100% APDEX is easy when there is nobody around.
+- HTTP status codes, with optional detailed output of the most frequent URLs
+  per error status code, along with their most frequent referers
+  Because your forgot to update a link to that conditionally-used browser
+  compatibility javascript you renamed.
+- Hottest pages (pages which use rendering time the most)
+  Because you want to know where to invest time to get highest user experience
+  improvement.
+- ERP5 sites: per-module statistics, with module and document views separated
+  Because module and document types are not born equal in usage patterns.
+Some parsing performance figures:
+On a 2.3Ghz Corei5, apachedex achieves 97000 lines/s (
+pypy-c-jit-62994-bd32583a3f11-linux64) and 43000 lines/s (CPython 2.7).
+Those were measures on a 3000000-hits logfile, with 3 --skip-base, 1
+--erp5-base, 3 --base and --default set. --\*base values were similar in
+simplicity to the ones provided in examples below.
+
+%package -n python3-APacheDEX
+Summary:	Compute APDEX from Apache-style logs.
+Provides:	python-APacheDEX
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-APacheDEX
+Parses Apache-style logs and generates several statistics intended for a
+website developer audience:
+- APDEX (Application Performance inDEX, see http://www.apdex.org) ratio
+  (plotted)
+  Because you want to know how satisfied your users are.
+- hit count (plotted)
+  Because achieving 100% APDEX is easy when there is nobody around.
+- HTTP status codes, with optional detailed output of the most frequent URLs
+  per error status code, along with their most frequent referers
+  Because your forgot to update a link to that conditionally-used browser
+  compatibility javascript you renamed.
+- Hottest pages (pages which use rendering time the most)
+  Because you want to know where to invest time to get highest user experience
+  improvement.
+- ERP5 sites: per-module statistics, with module and document views separated
+  Because module and document types are not born equal in usage patterns.
+Some parsing performance figures:
+On a 2.3Ghz Corei5, apachedex achieves 97000 lines/s (
+pypy-c-jit-62994-bd32583a3f11-linux64) and 43000 lines/s (CPython 2.7).
+Those were measures on a 3000000-hits logfile, with 3 --skip-base, 1
+--erp5-base, 3 --base and --default set. --\*base values were similar in
+simplicity to the ones provided in examples below.
+
+%package help
+Summary:	Development documents and examples for APacheDEX
+Provides:	python3-APacheDEX-doc
+%description help
+Parses Apache-style logs and generates several statistics intended for a
+website developer audience:
+- APDEX (Application Performance inDEX, see http://www.apdex.org) ratio
+  (plotted)
+  Because you want to know how satisfied your users are.
+- hit count (plotted)
+  Because achieving 100% APDEX is easy when there is nobody around.
+- HTTP status codes, with optional detailed output of the most frequent URLs
+  per error status code, along with their most frequent referers
+  Because your forgot to update a link to that conditionally-used browser
+  compatibility javascript you renamed.
+- Hottest pages (pages which use rendering time the most)
+  Because you want to know where to invest time to get highest user experience
+  improvement.
+- ERP5 sites: per-module statistics, with module and document views separated
+  Because module and document types are not born equal in usage patterns.
+Some parsing performance figures:
+On a 2.3Ghz Corei5, apachedex achieves 97000 lines/s (
+pypy-c-jit-62994-bd32583a3f11-linux64) and 43000 lines/s (CPython 2.7).
+Those were measures on a 3000000-hits logfile, with 3 --skip-base, 1
+--erp5-base, 3 --base and --default set. --\*base values were similar in
+simplicity to the ones provided in examples below.
+
+%prep
+%autosetup -n APacheDEX-1.8
+
+%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-APacheDEX -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Mon May 29 2023 Python_Bot <Python_Bot@openeuler.org> - 1.8-1
+- Package Spec generated