automatic import of python-xlib

3 files changed, 282 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..3614fed 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/xlib-0.21.tar.gz
diff --git a/python-xlib.spec b/python-xlib.spec
new file mode 100644
index 0000000..04082df
--- /dev/null
+++ b/python-xlib.spec
@@ -0,0 +1,280 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-xlib
+Version:	0.21
+Release:	1
+Summary:	Python X Library
+License:	LGPLv2+
+URL:		https://github.com/python-xlib/python-xlib
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/74/d4/6033a97f96fc7d7bb822dab52e2e3c9532256d7ce033fa9675734941b9ac/xlib-0.21.tar.gz
+BuildArch:	noarch
+
+Requires:	python3-six
+
+%description
+|Build Status| |codecov.io| |Code Health|
+`Homepage`_ | `Releases`_ | `Changelog`_
+Copyright
+~~~~~~~~~
+The main part of the code is
+    Copyright (C) 2000-2002  Peter Liljenberg
+Some contributed code is copyrighted by `the contributors <Contributors_>`_,
+in these cases that is indicated in the source files in question.
+The Python X Library is released under LGPL v2.1 or later (since 2016),
+see the file LICENSE for details. 0.15rc1 and before were released under
+GPL v2.
+Requirements
+~~~~~~~~~~~~
+The Python X Library requires Python 2.7 or newer. It has been tested to
+various extents with Python 2.7 and 3.3 through 3.6.
+Installation
+~~~~~~~~~~~~
+The Python Xlib uses the standard setuptools package, to install run
+this command:
+    python setup.py install
+See the command help for details: ``python setup.py install -h``.
+Alternatively, you can run programs from the distribution directory, or
+change the module path in programs.
+There's a simple example program, implemented twice using both the
+high-level interface and the low-level protocol.
+Introduction
+~~~~~~~~~~~~
+The Python X Library is intended to be a fully functional X client
+library for Python programs. It is written entirely in Python, in
+contrast to earlier X libraries for Python (the ancient X extension and
+the newer plxlib) which were interfaces to the C Xlib.
+This is possible to do since X client programs communicate with the X
+server via the X protocol. The communication takes place over TCP/IP,
+Unix sockets, DECnet or any other streaming network protocol. The C Xlib
+is merely an interface to this protocol, providing functions suitable
+for a C environment.
+There are three advantages of implementing a pure Python library:
+-  Integration: The library can make use of the wonderful object system
+   in Python, providing an easy-to-use class hierarchy.
+-  Portability: The library will be usable on (almost) any computer
+   which have Python installed. A C interface could be problematic to
+   port to non-Unix systems, such as MS Windows or OpenVMS.
+-  Maintainability: It is much easier to develop and debug native Python
+   modules than modules written in C.
+Documentation
+~~~~~~~~~~~~~
+The reference manual is not finished by far, but is probably still useful. It
+can be `browsed online <http://python-xlib.sourceforge.net/doc/html/index.html>`__.
+There are also some `example programs <Examples_>`_ and, of course,
+`the standard X11 documentation <http://tronche.com/gui/x/xlib/>`__ applies.
+Project status
+~~~~~~~~~~~~~~
+The low-level protocol is complete, implementing client-side X11R6. The
+high-level object oriented interface is also fully functional. It is
+possible to write client applications with the library. Currently, the
+only real application using Python Xlib is the window manager PLWM,
+starting with version 2.0.
+There is a resource database implementation, ICCCM support and a
+framework for adding X extension code. Several extensions have been
+implemented; (RECORD, SHAPE, Xinerama, Composite, RANDR, and XTEST)
+patches for additions are very welcome.
+There are most likely still bugs, but the library is at least stable
+enough to run PLWM. A continuously bigger part of the library is covered
+by regression tests, improving stability.
+The documentation is still quite rudimentary, but should be of some help
+for people programming with the Xlib. X beginners should first find some
+general texts on X. A very good starting point is
+http://www.rahul.net/kenton/xsites.html
+See the file TODO for a detailed list of what is missing, approximately
+ordered by importance.
+
+%package -n python3-xlib
+Summary:	Python X Library
+Provides:	python-xlib
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-xlib
+|Build Status| |codecov.io| |Code Health|
+`Homepage`_ | `Releases`_ | `Changelog`_
+Copyright
+~~~~~~~~~
+The main part of the code is
+    Copyright (C) 2000-2002  Peter Liljenberg
+Some contributed code is copyrighted by `the contributors <Contributors_>`_,
+in these cases that is indicated in the source files in question.
+The Python X Library is released under LGPL v2.1 or later (since 2016),
+see the file LICENSE for details. 0.15rc1 and before were released under
+GPL v2.
+Requirements
+~~~~~~~~~~~~
+The Python X Library requires Python 2.7 or newer. It has been tested to
+various extents with Python 2.7 and 3.3 through 3.6.
+Installation
+~~~~~~~~~~~~
+The Python Xlib uses the standard setuptools package, to install run
+this command:
+    python setup.py install
+See the command help for details: ``python setup.py install -h``.
+Alternatively, you can run programs from the distribution directory, or
+change the module path in programs.
+There's a simple example program, implemented twice using both the
+high-level interface and the low-level protocol.
+Introduction
+~~~~~~~~~~~~
+The Python X Library is intended to be a fully functional X client
+library for Python programs. It is written entirely in Python, in
+contrast to earlier X libraries for Python (the ancient X extension and
+the newer plxlib) which were interfaces to the C Xlib.
+This is possible to do since X client programs communicate with the X
+server via the X protocol. The communication takes place over TCP/IP,
+Unix sockets, DECnet or any other streaming network protocol. The C Xlib
+is merely an interface to this protocol, providing functions suitable
+for a C environment.
+There are three advantages of implementing a pure Python library:
+-  Integration: The library can make use of the wonderful object system
+   in Python, providing an easy-to-use class hierarchy.
+-  Portability: The library will be usable on (almost) any computer
+   which have Python installed. A C interface could be problematic to
+   port to non-Unix systems, such as MS Windows or OpenVMS.
+-  Maintainability: It is much easier to develop and debug native Python
+   modules than modules written in C.
+Documentation
+~~~~~~~~~~~~~
+The reference manual is not finished by far, but is probably still useful. It
+can be `browsed online <http://python-xlib.sourceforge.net/doc/html/index.html>`__.
+There are also some `example programs <Examples_>`_ and, of course,
+`the standard X11 documentation <http://tronche.com/gui/x/xlib/>`__ applies.
+Project status
+~~~~~~~~~~~~~~
+The low-level protocol is complete, implementing client-side X11R6. The
+high-level object oriented interface is also fully functional. It is
+possible to write client applications with the library. Currently, the
+only real application using Python Xlib is the window manager PLWM,
+starting with version 2.0.
+There is a resource database implementation, ICCCM support and a
+framework for adding X extension code. Several extensions have been
+implemented; (RECORD, SHAPE, Xinerama, Composite, RANDR, and XTEST)
+patches for additions are very welcome.
+There are most likely still bugs, but the library is at least stable
+enough to run PLWM. A continuously bigger part of the library is covered
+by regression tests, improving stability.
+The documentation is still quite rudimentary, but should be of some help
+for people programming with the Xlib. X beginners should first find some
+general texts on X. A very good starting point is
+http://www.rahul.net/kenton/xsites.html
+See the file TODO for a detailed list of what is missing, approximately
+ordered by importance.
+
+%package help
+Summary:	Development documents and examples for xlib
+Provides:	python3-xlib-doc
+%description help
+|Build Status| |codecov.io| |Code Health|
+`Homepage`_ | `Releases`_ | `Changelog`_
+Copyright
+~~~~~~~~~
+The main part of the code is
+    Copyright (C) 2000-2002  Peter Liljenberg
+Some contributed code is copyrighted by `the contributors <Contributors_>`_,
+in these cases that is indicated in the source files in question.
+The Python X Library is released under LGPL v2.1 or later (since 2016),
+see the file LICENSE for details. 0.15rc1 and before were released under
+GPL v2.
+Requirements
+~~~~~~~~~~~~
+The Python X Library requires Python 2.7 or newer. It has been tested to
+various extents with Python 2.7 and 3.3 through 3.6.
+Installation
+~~~~~~~~~~~~
+The Python Xlib uses the standard setuptools package, to install run
+this command:
+    python setup.py install
+See the command help for details: ``python setup.py install -h``.
+Alternatively, you can run programs from the distribution directory, or
+change the module path in programs.
+There's a simple example program, implemented twice using both the
+high-level interface and the low-level protocol.
+Introduction
+~~~~~~~~~~~~
+The Python X Library is intended to be a fully functional X client
+library for Python programs. It is written entirely in Python, in
+contrast to earlier X libraries for Python (the ancient X extension and
+the newer plxlib) which were interfaces to the C Xlib.
+This is possible to do since X client programs communicate with the X
+server via the X protocol. The communication takes place over TCP/IP,
+Unix sockets, DECnet or any other streaming network protocol. The C Xlib
+is merely an interface to this protocol, providing functions suitable
+for a C environment.
+There are three advantages of implementing a pure Python library:
+-  Integration: The library can make use of the wonderful object system
+   in Python, providing an easy-to-use class hierarchy.
+-  Portability: The library will be usable on (almost) any computer
+   which have Python installed. A C interface could be problematic to
+   port to non-Unix systems, such as MS Windows or OpenVMS.
+-  Maintainability: It is much easier to develop and debug native Python
+   modules than modules written in C.
+Documentation
+~~~~~~~~~~~~~
+The reference manual is not finished by far, but is probably still useful. It
+can be `browsed online <http://python-xlib.sourceforge.net/doc/html/index.html>`__.
+There are also some `example programs <Examples_>`_ and, of course,
+`the standard X11 documentation <http://tronche.com/gui/x/xlib/>`__ applies.
+Project status
+~~~~~~~~~~~~~~
+The low-level protocol is complete, implementing client-side X11R6. The
+high-level object oriented interface is also fully functional. It is
+possible to write client applications with the library. Currently, the
+only real application using Python Xlib is the window manager PLWM,
+starting with version 2.0.
+There is a resource database implementation, ICCCM support and a
+framework for adding X extension code. Several extensions have been
+implemented; (RECORD, SHAPE, Xinerama, Composite, RANDR, and XTEST)
+patches for additions are very welcome.
+There are most likely still bugs, but the library is at least stable
+enough to run PLWM. A continuously bigger part of the library is covered
+by regression tests, improving stability.
+The documentation is still quite rudimentary, but should be of some help
+for people programming with the Xlib. X beginners should first find some
+general texts on X. A very good starting point is
+http://www.rahul.net/kenton/xsites.html
+See the file TODO for a detailed list of what is missing, approximately
+ordered by importance.
+
+%prep
+%autosetup -n xlib-0.21
+
+%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-xlib -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Thu Mar 09 2023 Python_Bot <Python_Bot@openeuler.org> - 0.21-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..5a24d6c
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+8d1ccb3b070ae96f20c3750b49ced6b3  xlib-0.21.tar.gz