%global _empty_manifest_terminate_build 0
Name:		python-bibtexvcs
Version:	2015.16
Release:	1
Summary:	a Python package for managing a BibTeX database and related documents
License:	GPL3
URL:		http://github.com/supermihi/bibtevxcs
Source0:	https://mirrors.aliyun.com/pypi/web/packages/81/68/8b698151de95c1fa136211a039d559f20f2f352080dc277497b38e2dded5/bibtexvcs-2015.16.zip
BuildArch:	noarch


%description
Collecting and managing bibliography information can be cumbersone. Therefore it makes sense to maintain
a single BibTeX database within a research group that focusses on the same topic and thus has a lot of
common bibliography. Furthermore, tools like JabRef_ allow to link PDF documents to BibTeX entries, turning
the ``bib`` file into a valuable literature database.
Since the ``bib`` file is text-based, it can be efficiently put under revision control. However, such a database
used by several people over a long period of time tends to become messy. Furthermore, most people are not
trained, and even less interested in, the usage of VCS systems.
`BibTeX VCS` resolves these issues by automating the most common VCS operations and providing a minimalist,
platform-independent GUI. It allows to defined a number of `database checks` that are run prior to each
commit operation, in order to enforce consistency and a defined referencing style within the database.
For example, there is a check that ensures that the documents linked to BibTeX entries actually exist, and
each PDF document is linked to by at least one BibTeX entry. For information on the default checks and how to
add custom ones, see :ref:`checksModule`.

%package -n python3-bibtexvcs
Summary:	a Python package for managing a BibTeX database and related documents
Provides:	python-bibtexvcs
BuildRequires:	python3-devel
BuildRequires:	python3-setuptools
BuildRequires:	python3-pip
%description -n python3-bibtexvcs
Collecting and managing bibliography information can be cumbersone. Therefore it makes sense to maintain
a single BibTeX database within a research group that focusses on the same topic and thus has a lot of
common bibliography. Furthermore, tools like JabRef_ allow to link PDF documents to BibTeX entries, turning
the ``bib`` file into a valuable literature database.
Since the ``bib`` file is text-based, it can be efficiently put under revision control. However, such a database
used by several people over a long period of time tends to become messy. Furthermore, most people are not
trained, and even less interested in, the usage of VCS systems.
`BibTeX VCS` resolves these issues by automating the most common VCS operations and providing a minimalist,
platform-independent GUI. It allows to defined a number of `database checks` that are run prior to each
commit operation, in order to enforce consistency and a defined referencing style within the database.
For example, there is a check that ensures that the documents linked to BibTeX entries actually exist, and
each PDF document is linked to by at least one BibTeX entry. For information on the default checks and how to
add custom ones, see :ref:`checksModule`.

%package help
Summary:	Development documents and examples for bibtexvcs
Provides:	python3-bibtexvcs-doc
%description help
Collecting and managing bibliography information can be cumbersone. Therefore it makes sense to maintain
a single BibTeX database within a research group that focusses on the same topic and thus has a lot of
common bibliography. Furthermore, tools like JabRef_ allow to link PDF documents to BibTeX entries, turning
the ``bib`` file into a valuable literature database.
Since the ``bib`` file is text-based, it can be efficiently put under revision control. However, such a database
used by several people over a long period of time tends to become messy. Furthermore, most people are not
trained, and even less interested in, the usage of VCS systems.
`BibTeX VCS` resolves these issues by automating the most common VCS operations and providing a minimalist,
platform-independent GUI. It allows to defined a number of `database checks` that are run prior to each
commit operation, in order to enforce consistency and a defined referencing style within the database.
For example, there is a check that ensures that the documents linked to BibTeX entries actually exist, and
each PDF document is linked to by at least one BibTeX entry. For information on the default checks and how to
add custom ones, see :ref:`checksModule`.

%prep
%autosetup -n bibtexvcs-2015.16

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

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

%changelog
* Tue Jun 20 2023 Python_Bot <Python_Bot@openeuler.org> - 2015.16-1
- Package Spec generated