%global _empty_manifest_terminate_build 0 Name: python-aldryn-boilerplates Version: 0.8.0 Release: 1 Summary: An extension that allows re-usable apps to provide sets of templates and staticfiles for different boilerplates. License: BSD URL: https://github.com/aldryn/aldryn-boilerplates/ Source0: https://mirrors.nju.edu.cn/pypi/web/packages/ea/cb/a89e12228dc45b8e6c400803789227f33f113030ed79925b011a03d1889d/aldryn-boilerplates-0.8.0.tar.gz BuildArch: noarch %description In general configuration stays the same but you should respect changes that were introduced by django 1.8. In particular in Django 1.8 context processors were moved from ``django.core`` to ``django.template``. Be sure to include ``aldryn_boilerplates`` to ``INSTALLED_APPS``, adjust ``STATICFILES_FINDERS`` and finally configure ``TEMPLATES``. For ``TEMPLATES`` you need to add ``aldryn_boilerplates.context_processors.boilerplate`` to ``context_processors`` and alter ``loaders`` in the same way as we do it for Django versions prior to 1.8. **Note** that in the example below we are altering the default values, so if you are using something that is custom - don't forget to add that too. Here is an example of a simple configuration: INSTALLED_APPS = [ 'aldryn_boilerplates', ] STATICFILES_FINDERS = ( 'django.contrib.staticfiles.finders.FileSystemFinder', 'aldryn_boilerplates.staticfile_finders.AppDirectoriesFinder', 'django.contrib.staticfiles.finders.AppDirectoriesFinder', ) TEMPLATES = [ { 'BACKEND': 'django.template.backends.django.DjangoTemplates', 'OPTIONS': { 'context_processors': [ 'django.contrib.auth.context_processors.auth', 'django.contrib.messages.context_processors.messages', 'django.template.context_processors.i18n', 'django.template.context_processors.debug', 'django.template.context_processors.request', 'django.template.context_processors.media', 'django.template.context_processors.csrf', 'django.template.context_processors.tz', 'sekizai.context_processors.sekizai', 'django.template.context_processors.static', 'cms.context_processors.cms_settings', 'aldryn_boilerplates.context_processors.boilerplate', ], 'loaders': [ 'django.template.loaders.filesystem.Loader', 'aldryn_boilerplates.template_loaders.AppDirectoriesLoader', 'django.template.loaders.app_directories.Loader', ], }, }, ] ****************************************************** Adding aldryn-boilerplate support to existing packages ****************************************************** The recommended approach is to add a dependency to aldryn-boilerplates and to move existing ``static`` and ``template`` files to a boilerplate folder (completely remove ``static`` and ``templates``). If you're in the process of re-factoring your existing templates with something new, put them into the ``legacy`` boilerplate folder and set ``ALDRYN_BOILERPLATE_NAME='legacy'`` on projects that are still using the old templates. The new and shiny project can then use ``ALDRYN_BOILERPLATE_NAME='bootstrap3'`` to use the new Aldryn Bootstrap Boilerplate (`aldryn-boilerplate-bootstrap3`_). Or any other boilerplate for that matter. Removing ``static`` and ``templates`` has the benefit of removing likely deprecated templates from the very prominent location, that will confuse newcomers. It also prevents having not-relevant templates and static files messing up your setup. %package -n python3-aldryn-boilerplates Summary: An extension that allows re-usable apps to provide sets of templates and staticfiles for different boilerplates. Provides: python-aldryn-boilerplates BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-aldryn-boilerplates In general configuration stays the same but you should respect changes that were introduced by django 1.8. In particular in Django 1.8 context processors were moved from ``django.core`` to ``django.template``. Be sure to include ``aldryn_boilerplates`` to ``INSTALLED_APPS``, adjust ``STATICFILES_FINDERS`` and finally configure ``TEMPLATES``. For ``TEMPLATES`` you need to add ``aldryn_boilerplates.context_processors.boilerplate`` to ``context_processors`` and alter ``loaders`` in the same way as we do it for Django versions prior to 1.8. **Note** that in the example below we are altering the default values, so if you are using something that is custom - don't forget to add that too. Here is an example of a simple configuration: INSTALLED_APPS = [ 'aldryn_boilerplates', ] STATICFILES_FINDERS = ( 'django.contrib.staticfiles.finders.FileSystemFinder', 'aldryn_boilerplates.staticfile_finders.AppDirectoriesFinder', 'django.contrib.staticfiles.finders.AppDirectoriesFinder', ) TEMPLATES = [ { 'BACKEND': 'django.template.backends.django.DjangoTemplates', 'OPTIONS': { 'context_processors': [ 'django.contrib.auth.context_processors.auth', 'django.contrib.messages.context_processors.messages', 'django.template.context_processors.i18n', 'django.template.context_processors.debug', 'django.template.context_processors.request', 'django.template.context_processors.media', 'django.template.context_processors.csrf', 'django.template.context_processors.tz', 'sekizai.context_processors.sekizai', 'django.template.context_processors.static', 'cms.context_processors.cms_settings', 'aldryn_boilerplates.context_processors.boilerplate', ], 'loaders': [ 'django.template.loaders.filesystem.Loader', 'aldryn_boilerplates.template_loaders.AppDirectoriesLoader', 'django.template.loaders.app_directories.Loader', ], }, }, ] ****************************************************** Adding aldryn-boilerplate support to existing packages ****************************************************** The recommended approach is to add a dependency to aldryn-boilerplates and to move existing ``static`` and ``template`` files to a boilerplate folder (completely remove ``static`` and ``templates``). If you're in the process of re-factoring your existing templates with something new, put them into the ``legacy`` boilerplate folder and set ``ALDRYN_BOILERPLATE_NAME='legacy'`` on projects that are still using the old templates. The new and shiny project can then use ``ALDRYN_BOILERPLATE_NAME='bootstrap3'`` to use the new Aldryn Bootstrap Boilerplate (`aldryn-boilerplate-bootstrap3`_). Or any other boilerplate for that matter. Removing ``static`` and ``templates`` has the benefit of removing likely deprecated templates from the very prominent location, that will confuse newcomers. It also prevents having not-relevant templates and static files messing up your setup. %package help Summary: Development documents and examples for aldryn-boilerplates Provides: python3-aldryn-boilerplates-doc %description help In general configuration stays the same but you should respect changes that were introduced by django 1.8. In particular in Django 1.8 context processors were moved from ``django.core`` to ``django.template``. Be sure to include ``aldryn_boilerplates`` to ``INSTALLED_APPS``, adjust ``STATICFILES_FINDERS`` and finally configure ``TEMPLATES``. For ``TEMPLATES`` you need to add ``aldryn_boilerplates.context_processors.boilerplate`` to ``context_processors`` and alter ``loaders`` in the same way as we do it for Django versions prior to 1.8. **Note** that in the example below we are altering the default values, so if you are using something that is custom - don't forget to add that too. Here is an example of a simple configuration: INSTALLED_APPS = [ 'aldryn_boilerplates', ] STATICFILES_FINDERS = ( 'django.contrib.staticfiles.finders.FileSystemFinder', 'aldryn_boilerplates.staticfile_finders.AppDirectoriesFinder', 'django.contrib.staticfiles.finders.AppDirectoriesFinder', ) TEMPLATES = [ { 'BACKEND': 'django.template.backends.django.DjangoTemplates', 'OPTIONS': { 'context_processors': [ 'django.contrib.auth.context_processors.auth', 'django.contrib.messages.context_processors.messages', 'django.template.context_processors.i18n', 'django.template.context_processors.debug', 'django.template.context_processors.request', 'django.template.context_processors.media', 'django.template.context_processors.csrf', 'django.template.context_processors.tz', 'sekizai.context_processors.sekizai', 'django.template.context_processors.static', 'cms.context_processors.cms_settings', 'aldryn_boilerplates.context_processors.boilerplate', ], 'loaders': [ 'django.template.loaders.filesystem.Loader', 'aldryn_boilerplates.template_loaders.AppDirectoriesLoader', 'django.template.loaders.app_directories.Loader', ], }, }, ] ****************************************************** Adding aldryn-boilerplate support to existing packages ****************************************************** The recommended approach is to add a dependency to aldryn-boilerplates and to move existing ``static`` and ``template`` files to a boilerplate folder (completely remove ``static`` and ``templates``). If you're in the process of re-factoring your existing templates with something new, put them into the ``legacy`` boilerplate folder and set ``ALDRYN_BOILERPLATE_NAME='legacy'`` on projects that are still using the old templates. The new and shiny project can then use ``ALDRYN_BOILERPLATE_NAME='bootstrap3'`` to use the new Aldryn Bootstrap Boilerplate (`aldryn-boilerplate-bootstrap3`_). Or any other boilerplate for that matter. Removing ``static`` and ``templates`` has the benefit of removing likely deprecated templates from the very prominent location, that will confuse newcomers. It also prevents having not-relevant templates and static files messing up your setup. %prep %autosetup -n aldryn-boilerplates-0.8.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-aldryn-boilerplates -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Fri May 05 2023 Python_Bot - 0.8.0-1 - Package Spec generated