diff options
Diffstat (limited to 'python-ocrd-utils.spec')
| -rw-r--r-- | python-ocrd-utils.spec | 171 |
1 files changed, 171 insertions, 0 deletions
diff --git a/python-ocrd-utils.spec b/python-ocrd-utils.spec new file mode 100644 index 0000000..5339e76 --- /dev/null +++ b/python-ocrd-utils.spec @@ -0,0 +1,171 @@ +%global _empty_manifest_terminate_build 0 +Name: python-ocrd-utils +Version: 2.50.0 +Release: 1 +Summary: OCR-D framework - shared code, helpers, constants +License: Apache License 2.0 +URL: https://github.com/OCR-D/core +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/5d/f4/b45a38d8f02891bac8be4635a40fef7135f79cc4397bc656e20d7bb1dc61/ocrd_utils-2.50.0.tar.gz +BuildArch: noarch + +Requires: python3-Pillow +Requires: python3-numpy +Requires: python3-atomicwrites +Requires: python3-frozendict +Requires: python3-importlib-metadata +Requires: python3-importlib-resources + +%description +# ocrd_utils + +> OCR-D framework - shared code, helpers, constants + +## OCR-D Module Logging + +File-based control over logging facilities is done with standard [Python 3 logging module configuration files](https://docs.python.org/3.6/howto/logging.html#configuring-logging). This way, the level, format and destinations of log messages can be customized for all OCR-D modules individually and persistently, in the usual syntax. + +A template configuration file (with commented examples) is included in [ocrd_logging.conf](./ocrd_logging.conf). This is meant as an example, and should be **customized**. + +To get into effect, you must put a copy (under the same name) into: +1. your current working directory, +2. your user directory, or +3. `/etc`. +These directories are searched in said order, and the first find wins. When no config file is found, the default logging configuration applies (which uses only stdout and the `INFO` loglevel for most loggers, cf. [here](./ocrd_logging.py)). + +Thus, a configuration file will override *all* settings from the default configuration, and from configuration files in lower-priority directories. + +For more information about logging, handlers and formats, see [Python documentation](https://docs.python.org/3/howto/logging.htm). + +#### Docker containers + +In the Dockerfiles used to build `ocrd/core` (and subsequently `ocrd/all`), the above mentioned template is directly copied to `/etc/ocrd_logging.conf` within the container image. This configuration is thereby also the default configuration for OCR-D containers. + +Thus, if you want to customize logging rules in one of these Docker containers, you can create a custom configuration file and either: +- place it into your local workspace directory when running the OCR-D container. +- mount it under `/etc` when starting up the container, e.g. `docker run --mount type=bind,source=host/path/to/your-template.conf,destination=/etc/ocrd_logging.conf ocrd/all` +- include a Dockerfile step (layer or stage) which copies this into `/etc/ocrd_logging.conf` at build time in your own Docker image. + + +See also: https://github.com/OCR-D/core + + +%package -n python3-ocrd-utils +Summary: OCR-D framework - shared code, helpers, constants +Provides: python-ocrd-utils +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-ocrd-utils +# ocrd_utils + +> OCR-D framework - shared code, helpers, constants + +## OCR-D Module Logging + +File-based control over logging facilities is done with standard [Python 3 logging module configuration files](https://docs.python.org/3.6/howto/logging.html#configuring-logging). This way, the level, format and destinations of log messages can be customized for all OCR-D modules individually and persistently, in the usual syntax. + +A template configuration file (with commented examples) is included in [ocrd_logging.conf](./ocrd_logging.conf). This is meant as an example, and should be **customized**. + +To get into effect, you must put a copy (under the same name) into: +1. your current working directory, +2. your user directory, or +3. `/etc`. +These directories are searched in said order, and the first find wins. When no config file is found, the default logging configuration applies (which uses only stdout and the `INFO` loglevel for most loggers, cf. [here](./ocrd_logging.py)). + +Thus, a configuration file will override *all* settings from the default configuration, and from configuration files in lower-priority directories. + +For more information about logging, handlers and formats, see [Python documentation](https://docs.python.org/3/howto/logging.htm). + +#### Docker containers + +In the Dockerfiles used to build `ocrd/core` (and subsequently `ocrd/all`), the above mentioned template is directly copied to `/etc/ocrd_logging.conf` within the container image. This configuration is thereby also the default configuration for OCR-D containers. + +Thus, if you want to customize logging rules in one of these Docker containers, you can create a custom configuration file and either: +- place it into your local workspace directory when running the OCR-D container. +- mount it under `/etc` when starting up the container, e.g. `docker run --mount type=bind,source=host/path/to/your-template.conf,destination=/etc/ocrd_logging.conf ocrd/all` +- include a Dockerfile step (layer or stage) which copies this into `/etc/ocrd_logging.conf` at build time in your own Docker image. + + +See also: https://github.com/OCR-D/core + + +%package help +Summary: Development documents and examples for ocrd-utils +Provides: python3-ocrd-utils-doc +%description help +# ocrd_utils + +> OCR-D framework - shared code, helpers, constants + +## OCR-D Module Logging + +File-based control over logging facilities is done with standard [Python 3 logging module configuration files](https://docs.python.org/3.6/howto/logging.html#configuring-logging). This way, the level, format and destinations of log messages can be customized for all OCR-D modules individually and persistently, in the usual syntax. + +A template configuration file (with commented examples) is included in [ocrd_logging.conf](./ocrd_logging.conf). This is meant as an example, and should be **customized**. + +To get into effect, you must put a copy (under the same name) into: +1. your current working directory, +2. your user directory, or +3. `/etc`. +These directories are searched in said order, and the first find wins. When no config file is found, the default logging configuration applies (which uses only stdout and the `INFO` loglevel for most loggers, cf. [here](./ocrd_logging.py)). + +Thus, a configuration file will override *all* settings from the default configuration, and from configuration files in lower-priority directories. + +For more information about logging, handlers and formats, see [Python documentation](https://docs.python.org/3/howto/logging.htm). + +#### Docker containers + +In the Dockerfiles used to build `ocrd/core` (and subsequently `ocrd/all`), the above mentioned template is directly copied to `/etc/ocrd_logging.conf` within the container image. This configuration is thereby also the default configuration for OCR-D containers. + +Thus, if you want to customize logging rules in one of these Docker containers, you can create a custom configuration file and either: +- place it into your local workspace directory when running the OCR-D container. +- mount it under `/etc` when starting up the container, e.g. `docker run --mount type=bind,source=host/path/to/your-template.conf,destination=/etc/ocrd_logging.conf ocrd/all` +- include a Dockerfile step (layer or stage) which copies this into `/etc/ocrd_logging.conf` at build time in your own Docker image. + + +See also: https://github.com/OCR-D/core + + +%prep +%autosetup -n ocrd-utils-2.50.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-ocrd-utils -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 2.50.0-1 +- Package Spec generated |