automatic import of python-django-analytical

3 files changed, 113 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..1f2bde2 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/django-analytical-3.1.0.tar.gz
diff --git a/python-django-analytical.spec b/python-django-analytical.spec
new file mode 100644
index 0000000..2b88f58
--- /dev/null
+++ b/python-django-analytical.spec
@@ -0,0 +1,111 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-django-analytical
+Version:	3.1.0
+Release:	1
+Summary:	Analytics service integration for Django projects
+License:	MIT License
+URL:		https://github.com/jazzband/django-analytical
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/22/a4/220c10a3e1838811cc9bdc0227f371ada73d3aa30c882fc3903bed82594a/django-analytical-3.1.0.tar.gz
+BuildArch:	noarch
+
+
+%description
+|build-status| |coverage| |python-support| |license| |gitter| |jazzband|
+The django-analytical application integrates analytics services into a
+Django_ project.
+Using an analytics service with a Django project means adding Javascript
+tracking code to the project templates.  Of course, every service has
+its own specific installation instructions.  Furthermore, you need to
+include your unique identifiers, which then end up in the templates.
+Not very nice.
+This application hides the details of the different analytics services
+behind a generic interface, and keeps personal information and
+configuration out of the templates.  Its goal is to make the basic
+set-up very simple, while allowing advanced users to customize tracking.
+Each service is set up as recommended by the services themselves, using
+an asynchronous version of the Javascript code if possible.
+
+%package -n python3-django-analytical
+Summary:	Analytics service integration for Django projects
+Provides:	python-django-analytical
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-django-analytical
+|build-status| |coverage| |python-support| |license| |gitter| |jazzband|
+The django-analytical application integrates analytics services into a
+Django_ project.
+Using an analytics service with a Django project means adding Javascript
+tracking code to the project templates.  Of course, every service has
+its own specific installation instructions.  Furthermore, you need to
+include your unique identifiers, which then end up in the templates.
+Not very nice.
+This application hides the details of the different analytics services
+behind a generic interface, and keeps personal information and
+configuration out of the templates.  Its goal is to make the basic
+set-up very simple, while allowing advanced users to customize tracking.
+Each service is set up as recommended by the services themselves, using
+an asynchronous version of the Javascript code if possible.
+
+%package help
+Summary:	Development documents and examples for django-analytical
+Provides:	python3-django-analytical-doc
+%description help
+|build-status| |coverage| |python-support| |license| |gitter| |jazzband|
+The django-analytical application integrates analytics services into a
+Django_ project.
+Using an analytics service with a Django project means adding Javascript
+tracking code to the project templates.  Of course, every service has
+its own specific installation instructions.  Furthermore, you need to
+include your unique identifiers, which then end up in the templates.
+Not very nice.
+This application hides the details of the different analytics services
+behind a generic interface, and keeps personal information and
+configuration out of the templates.  Its goal is to make the basic
+set-up very simple, while allowing advanced users to customize tracking.
+Each service is set up as recommended by the services themselves, using
+an asynchronous version of the Javascript code if possible.
+
+%prep
+%autosetup -n django-analytical-3.1.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-django-analytical -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Tue Apr 11 2023 Python_Bot <Python_Bot@openeuler.org> - 3.1.0-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..9376a60
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+23adc3cf5956963c96f5c77402f78edf  django-analytical-3.1.0.tar.gz