diff options
| -rw-r--r-- | .gitignore | 1 | ||||
| -rw-r--r-- | python-notify2.spec | 108 | ||||
| -rw-r--r-- | sources | 1 |
3 files changed, 110 insertions, 0 deletions
@@ -0,0 +1 @@ +/notify2-0.3.1.tar.gz diff --git a/python-notify2.spec b/python-notify2.spec new file mode 100644 index 0000000..7458a00 --- /dev/null +++ b/python-notify2.spec @@ -0,0 +1,108 @@ +%global _empty_manifest_terminate_build 0 +Name: python-notify2 +Version: 0.3.1 +Release: 1 +Summary: Python interface to DBus notifications +License: BSD License +URL: https://bitbucket.org/takluyver/pynotify2 +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/aa/e8/d4b335aa739dc299a77766ecc5f1972d1de1993524aa94acef3219bba315/notify2-0.3.1.tar.gz +BuildArch: noarch + + +%description +There are a few differences from pynotify you should be aware of: +- If you need callbacks from notifications, notify2 must know about your event + loop. The simplest way is to pass 'glib' or 'qt' as the ``mainloop`` parameter + to ``init``. +- The methods ``attach_to_widget`` and ``attach_to_status_icon`` are not + implemented. You can calculate the location you want the notification to + appear and call ``Notification``. +- ``set_property`` and ``get_property`` are not implemented. The summary, body + and icon are accessible as attributes of a ``Notification`` instance. +- Various methods that pynotify Notification instances got from gobject do not + exist, or only implement part of the functionality. +Several pynotify functions, especially getters and setters, are only supported +for compatibility. You are encouraged to use more direct, Pythonic alternatives. + +%package -n python3-notify2 +Summary: Python interface to DBus notifications +Provides: python-notify2 +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-notify2 +There are a few differences from pynotify you should be aware of: +- If you need callbacks from notifications, notify2 must know about your event + loop. The simplest way is to pass 'glib' or 'qt' as the ``mainloop`` parameter + to ``init``. +- The methods ``attach_to_widget`` and ``attach_to_status_icon`` are not + implemented. You can calculate the location you want the notification to + appear and call ``Notification``. +- ``set_property`` and ``get_property`` are not implemented. The summary, body + and icon are accessible as attributes of a ``Notification`` instance. +- Various methods that pynotify Notification instances got from gobject do not + exist, or only implement part of the functionality. +Several pynotify functions, especially getters and setters, are only supported +for compatibility. You are encouraged to use more direct, Pythonic alternatives. + +%package help +Summary: Development documents and examples for notify2 +Provides: python3-notify2-doc +%description help +There are a few differences from pynotify you should be aware of: +- If you need callbacks from notifications, notify2 must know about your event + loop. The simplest way is to pass 'glib' or 'qt' as the ``mainloop`` parameter + to ``init``. +- The methods ``attach_to_widget`` and ``attach_to_status_icon`` are not + implemented. You can calculate the location you want the notification to + appear and call ``Notification``. +- ``set_property`` and ``get_property`` are not implemented. The summary, body + and icon are accessible as attributes of a ``Notification`` instance. +- Various methods that pynotify Notification instances got from gobject do not + exist, or only implement part of the functionality. +Several pynotify functions, especially getters and setters, are only supported +for compatibility. You are encouraged to use more direct, Pythonic alternatives. + +%prep +%autosetup -n notify2-0.3.1 + +%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-notify2 -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Thu Mar 09 2023 Python_Bot <Python_Bot@openeuler.org> - 0.3.1-1 +- Package Spec generated @@ -0,0 +1 @@ +ffccaed9330787c7442b453f6520a474 notify2-0.3.1.tar.gz |