1 |
%define github_name smarty |
2 |
|
3 |
%define php_libdir %{_datadir}/php |
4 |
|
5 |
%define __requires_exclude_from ^%{_datadir}/.*$ |
6 |
|
7 |
Name: php-smarty |
8 |
Version: 4.2.1 |
9 |
Release: %mkrel 1 |
10 |
Summary: Template/Presentation Framework for PHP |
11 |
License: LGPLv2+ |
12 |
Group: Development/PHP |
13 |
Url: http://www.smarty.net/ |
14 |
Source0: https://github.com/smarty-php/smarty/archive/v%{version}.tar.gz |
15 |
#until 3.1.32 |
16 |
#Patch0: CVE-2017-1000480.diff |
17 |
Requires: php-mbstring |
18 |
Requires: php-pcre |
19 |
Provides: php-composer(smarty/smarty) = %{version} |
20 |
Buildarch: noarch |
21 |
|
22 |
%description |
23 |
Although Smarty is known as a "Template Engine", it would be more accurately |
24 |
described as a "Template/Presentation Framework." That is, it provides the |
25 |
programmer and template designer with a wealth of tools to automate tasks |
26 |
commonly dealt with at the presentation layer of an application. I stress the |
27 |
word Framework because Smarty is not a simple tag-replacing template engine. |
28 |
Although it can be used for such a simple purpose, its focus is on quick and |
29 |
painless development and deployment of your application, while maintaining |
30 |
high-performance, scalability, security and future growth. |
31 |
|
32 |
%prep |
33 |
%setup -q -n %{github_name}-%{version} |
34 |
%autopatch -p1 |
35 |
|
36 |
%build |
37 |
|
38 |
%install |
39 |
mkdir -p %{buildroot}%{php_libdir} |
40 |
cp -pr libs %{buildroot}%{php_libdir}/Smarty |
41 |
|
42 |
%files |
43 |
%{php_libdir}/Smarty |