%global _empty_manifest_terminate_build 0 Name: python-django-notifications-hq Version: 1.7.0 Release: 1 Summary: GitHub notifications alike app for Django. License: MIT URL: http://github.com/django-notifications/django-notifications Source0: https://mirrors.nju.edu.cn/pypi/web/packages/27/9f/7d71e83b3de139aa7710732412cec6014613cd30c41d20d9e9b1b0de6c76/django-notifications-hq-1.7.0.tar.gz BuildArch: noarch Requires: python3-django Requires: python3-django-model-utils Requires: python3-jsonfield Requires: python3-pytz Requires: python3-swapper %description |build-status| |coveralls| `django-notifications `_ is a GitHub notification alike app for Django, it was derived from `django-activity-stream `_ The major difference between ``django-notifications`` and ``django-activity-stream``: * ``django-notifications`` is for building something like Github "Notifications" * While ``django-activity-stream`` is for building Github "News Feed" Notifications are actually actions events, which are categorized by four main components. * ``Actor``. The object that performed the activity. * ``Verb``. The verb phrase that identifies the action of the activity. * ``Action Object``. *(Optional)* The object linked to the action itself. * ``Target``. *(Optional)* The object to which the activity was performed. ``Actor``, ``Action Object`` and ``Target`` are ``GenericForeignKeys`` to any arbitrary Django object. An action is a description of an action that was performed (``Verb``) at some instant in time by some ``Actor`` on some optional ``Target`` that results in an ``Action Object`` getting created/updated/deleted. For example: `justquick `_ ``(actor)`` *closed* ``(verb)`` `issue 2 `_ ``(action_object)`` on `activity-stream `_ ``(target)`` 12 hours ago Nomenclature of this specification is based on the Activity Streams Spec: ``_ %package -n python3-django-notifications-hq Summary: GitHub notifications alike app for Django. Provides: python-django-notifications-hq BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-django-notifications-hq |build-status| |coveralls| `django-notifications `_ is a GitHub notification alike app for Django, it was derived from `django-activity-stream `_ The major difference between ``django-notifications`` and ``django-activity-stream``: * ``django-notifications`` is for building something like Github "Notifications" * While ``django-activity-stream`` is for building Github "News Feed" Notifications are actually actions events, which are categorized by four main components. * ``Actor``. The object that performed the activity. * ``Verb``. The verb phrase that identifies the action of the activity. * ``Action Object``. *(Optional)* The object linked to the action itself. * ``Target``. *(Optional)* The object to which the activity was performed. ``Actor``, ``Action Object`` and ``Target`` are ``GenericForeignKeys`` to any arbitrary Django object. An action is a description of an action that was performed (``Verb``) at some instant in time by some ``Actor`` on some optional ``Target`` that results in an ``Action Object`` getting created/updated/deleted. For example: `justquick `_ ``(actor)`` *closed* ``(verb)`` `issue 2 `_ ``(action_object)`` on `activity-stream `_ ``(target)`` 12 hours ago Nomenclature of this specification is based on the Activity Streams Spec: ``_ %package help Summary: Development documents and examples for django-notifications-hq Provides: python3-django-notifications-hq-doc %description help |build-status| |coveralls| `django-notifications `_ is a GitHub notification alike app for Django, it was derived from `django-activity-stream `_ The major difference between ``django-notifications`` and ``django-activity-stream``: * ``django-notifications`` is for building something like Github "Notifications" * While ``django-activity-stream`` is for building Github "News Feed" Notifications are actually actions events, which are categorized by four main components. * ``Actor``. The object that performed the activity. * ``Verb``. The verb phrase that identifies the action of the activity. * ``Action Object``. *(Optional)* The object linked to the action itself. * ``Target``. *(Optional)* The object to which the activity was performed. ``Actor``, ``Action Object`` and ``Target`` are ``GenericForeignKeys`` to any arbitrary Django object. An action is a description of an action that was performed (``Verb``) at some instant in time by some ``Actor`` on some optional ``Target`` that results in an ``Action Object`` getting created/updated/deleted. For example: `justquick `_ ``(actor)`` *closed* ``(verb)`` `issue 2 `_ ``(action_object)`` on `activity-stream `_ ``(target)`` 12 hours ago Nomenclature of this specification is based on the Activity Streams Spec: ``_ %prep %autosetup -n django-notifications-hq-1.7.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-django-notifications-hq -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Sun Apr 23 2023 Python_Bot - 1.7.0-1 - Package Spec generated