automatic import of python-django-lineageopeneuler20.03

3 files changed, 116 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..c44389f 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/django-lineage-0.2.0.tar.gz
diff --git a/python-django-lineage.spec b/python-django-lineage.spec
new file mode 100644
index 0000000..e3021d1
--- /dev/null
+++ b/python-django-lineage.spec
@@ -0,0 +1,114 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-django-lineage
+Version:	0.2.0
+Release:	1
+Summary:	Lightweight template tags for neater hierarchical navigation
+License:	BSD
+URL:		https://github.com/marcuswhybrow/django-lineage
+Source0:	https://mirrors.aliyun.com/pypi/web/packages/b3/f5/86f8ebe522c63118b6d43bae750f1fbea970eef16ec90cad6a5bafa88070/django-lineage-0.2.0.tar.gz
+BuildArch:	noarch
+
+
+%description
+Handling which navigation element is active in a particular template can become
+annoying. Template blocks can be defined and later overriden to "activate" a
+class on a particular navigational element, **but thats gets ugly!**
+**Lineage makes things neater** by defining your conditions centrally, and it
+looks like this::
+  {% load lineage %}
+  <ul>
+      <li class="{% ancestor '/home/' %}"><a href="/home/">Home</a></li>
+      <li class="{% ancestor '/blog/' %}"><a href="/blog/">Blog</a></li>
+      <li class="{% ancestor '/about/' %}"><a href="/about/">About</a></li>
+  </ul>
+When an ``ancestor`` tag is evaludated, it compares it's argument to the page URL.
+If the argument string matches the start of the current pages URL, it outputs
+"active". **It's that simple!**
+Read on for accepted arguments:
+
+%package -n python3-django-lineage
+Summary:	Lightweight template tags for neater hierarchical navigation
+Provides:	python-django-lineage
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-django-lineage
+Handling which navigation element is active in a particular template can become
+annoying. Template blocks can be defined and later overriden to "activate" a
+class on a particular navigational element, **but thats gets ugly!**
+**Lineage makes things neater** by defining your conditions centrally, and it
+looks like this::
+  {% load lineage %}
+  <ul>
+      <li class="{% ancestor '/home/' %}"><a href="/home/">Home</a></li>
+      <li class="{% ancestor '/blog/' %}"><a href="/blog/">Blog</a></li>
+      <li class="{% ancestor '/about/' %}"><a href="/about/">About</a></li>
+  </ul>
+When an ``ancestor`` tag is evaludated, it compares it's argument to the page URL.
+If the argument string matches the start of the current pages URL, it outputs
+"active". **It's that simple!**
+Read on for accepted arguments:
+
+%package help
+Summary:	Development documents and examples for django-lineage
+Provides:	python3-django-lineage-doc
+%description help
+Handling which navigation element is active in a particular template can become
+annoying. Template blocks can be defined and later overriden to "activate" a
+class on a particular navigational element, **but thats gets ugly!**
+**Lineage makes things neater** by defining your conditions centrally, and it
+looks like this::
+  {% load lineage %}
+  <ul>
+      <li class="{% ancestor '/home/' %}"><a href="/home/">Home</a></li>
+      <li class="{% ancestor '/blog/' %}"><a href="/blog/">Blog</a></li>
+      <li class="{% ancestor '/about/' %}"><a href="/about/">About</a></li>
+  </ul>
+When an ``ancestor`` tag is evaludated, it compares it's argument to the page URL.
+If the argument string matches the start of the current pages URL, it outputs
+"active". **It's that simple!**
+Read on for accepted arguments:
+
+%prep
+%autosetup -n django-lineage-0.2.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-lineage -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Tue Jun 20 2023 Python_Bot <Python_Bot@openeuler.org> - 0.2.0-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..9da8eec
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+a92910bf0ea69427880769ab8f05b0cf  django-lineage-0.2.0.tar.gz