package init
This commit is contained in:
parent
804697169d
commit
fe4aa9c63b
BIN
5.0.1.tar.gz
Normal file
BIN
5.0.1.tar.gz
Normal file
Binary file not shown.
110
python-zope.i18nmessageid.spec
Normal file
110
python-zope.i18nmessageid.spec
Normal file
@ -0,0 +1,110 @@
|
||||
%global _empty_manifest_terminate_build 0
|
||||
Name: python-zope.i18nmessageid
|
||||
Version: 5.0.1
|
||||
Release: 1
|
||||
Summary: Message Identifiers for internationalization
|
||||
License: ZPL 2.1
|
||||
URL: https://github.com/zopefoundation/zope.i18nmessageid
|
||||
Source0: https://github.com/zopefoundation/zope.i18nmessageid/archive/%{version}.tar.gz
|
||||
|
||||
%description
|
||||
To translate any text, we must be able to discover the source domain
|
||||
of the text. A source domain is an identifier that identifies a
|
||||
project that produces program source strings. Source strings occur as
|
||||
literals in python programs, text in templates, and some text in XML
|
||||
data. The project implies a source language and an application
|
||||
context.
|
||||
We can think of a source domain as a collection of messages and
|
||||
associated translation strings.
|
||||
We often need to create unicode strings that will be displayed by
|
||||
separate views. The view cannot translate the string without knowing
|
||||
its source domain. A string or unicode literal carries no domain
|
||||
information, therefore we use messages. Messages are unicode strings
|
||||
which carry a translation source domain and possibly a default
|
||||
translation. They are created by a message factory. The message
|
||||
factory is created by calling ``MessageFactory`` with the source
|
||||
domain.
|
||||
This package provides facilities for *declaring* such messages within
|
||||
program source text; translation of the messages is the responsiblitiy
|
||||
of the 'zope.i18n' package.
|
||||
|
||||
%package -n python3-zope.i18nmessageid
|
||||
Summary: Message Identifiers for internationalization
|
||||
Provides: python-zope.i18nmessageid
|
||||
BuildRequires: python3-devel
|
||||
BuildRequires: python3-setuptools
|
||||
BuildRequires: python3-cffi
|
||||
BuildRequires: gcc
|
||||
BuildRequires: gdb
|
||||
|
||||
%description -n python3-zope.i18nmessageid
|
||||
To translate any text, we must be able to discover the source domain
|
||||
of the text. A source domain is an identifier that identifies a
|
||||
project that produces program source strings. Source strings occur as
|
||||
literals in python programs, text in templates, and some text in XML
|
||||
data. The project implies a source language and an application
|
||||
context.
|
||||
We can think of a source domain as a collection of messages and
|
||||
associated translation strings.
|
||||
We often need to create unicode strings that will be displayed by
|
||||
separate views. The view cannot translate the string without knowing
|
||||
its source domain. A string or unicode literal carries no domain
|
||||
information, therefore we use messages. Messages are unicode strings
|
||||
which carry a translation source domain and possibly a default
|
||||
translation. They are created by a message factory. The message
|
||||
factory is created by calling ``MessageFactory`` with the source
|
||||
domain.
|
||||
This package provides facilities for *declaring* such messages within
|
||||
program source text; translation of the messages is the responsiblitiy
|
||||
of the 'zope.i18n' package.
|
||||
|
||||
%package help
|
||||
Summary: Development documents and examples for zope.i18nmessageid
|
||||
Provides: python3-zope.i18nmessageid-doc
|
||||
|
||||
%description help
|
||||
Development documents and examples for zope.i18nmessageid.
|
||||
|
||||
%prep
|
||||
%autosetup -n zope.i18nmessageid-%{version}
|
||||
|
||||
%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-zope.i18nmessageid -f filelist.lst
|
||||
%dir %{python3_sitearch}/*
|
||||
|
||||
%files help -f doclist.lst
|
||||
%{_pkgdocdir}
|
||||
|
||||
%changelog
|
||||
* Thu Dec 17 2020 Python_Bot <Python_Bot@openeuler.org>
|
||||
- Package Spec generated
|
||||
4
python-zope.i18nmessageid.yaml
Normal file
4
python-zope.i18nmessageid.yaml
Normal file
@ -0,0 +1,4 @@
|
||||
version_control: github
|
||||
src_repo: zopefoundation/zope.i18nmessageid
|
||||
tag_prefix: "^"
|
||||
separator: "."
|
||||
Loading…
x
Reference in New Issue
Block a user