Accepting request 295730 from devel:languages:perl:autoupdate
update OBS-URL: https://build.opensuse.org/request/show/295730 OBS-URL: https://build.opensuse.org/package/show/devel:languages:perl/perl-HTML-Template-Compiled?expand=0&rev=2
This commit is contained in:
@@ -1,7 +1,7 @@
|
||||
#
|
||||
# spec file for package perl-HTML-Template-Compiled (Version 0.95)
|
||||
# spec file for package perl-HTML-Template-Compiled
|
||||
#
|
||||
# Copyright (c) 2011 SUSE LINUX Products GmbH, Nuernberg, Germany.
|
||||
# Copyright (c) 2015 SUSE LINUX GmbH, Nuernberg, Germany.
|
||||
#
|
||||
# All modifications and additions to the file contributed by third parties
|
||||
# remain the property of their copyright owners, unless otherwise agreed
|
||||
@@ -15,49 +15,66 @@
|
||||
# Please submit bugfixes or comments via http://bugs.opensuse.org/
|
||||
#
|
||||
|
||||
|
||||
Name: perl-HTML-Template-Compiled
|
||||
Version: 0.95
|
||||
Release: 1
|
||||
License: GPL+ or Artistic
|
||||
Version: 1.001
|
||||
Release: 0
|
||||
%define cpan_name HTML-Template-Compiled
|
||||
Summary: Template System Compiles HTML::Template files to Perl code
|
||||
Url: http://search.cpan.org/dist/HTML-Template-Compiled/
|
||||
License: Artistic-1.0 or GPL-1.0+
|
||||
Group: Development/Libraries/Perl
|
||||
Url: http://search.cpan.org/dist/HTML-Template-Compiled/
|
||||
Source: http://www.cpan.org/authors/id/T/TI/TINITA/%{cpan_name}-%{version}.tar.gz
|
||||
BuildArch: noarch
|
||||
BuildRoot: %{_tmppath}/%{name}-%{version}-build
|
||||
BuildRequires: perl
|
||||
BuildRequires: perl-macros
|
||||
BuildRequires: perl(Module::Build)
|
||||
Recommends: perl(URI::Escape)
|
||||
BuildRequires: perl(Module::Build) >= 0.28
|
||||
BuildRequires: perl(URI::Escape)
|
||||
Requires: perl(URI::Escape)
|
||||
Recommends: perl(Parse::RecDescent)
|
||||
%{perl_requires}
|
||||
|
||||
%description
|
||||
HTML::Template::Compiled is a template system which can be used for the
|
||||
HTML::Template manpage templates with almost the same API. It offers more
|
||||
flexible template delimiters, additional tags and features, and by
|
||||
compiling the template into perl code it can run significantly faster in
|
||||
persistent environments such as FastCGI or mod_perl.
|
||||
|
||||
The goal is to offer more features for flexibility but keep the basic
|
||||
syntax as easy as it is.
|
||||
|
||||
Features at a glance:
|
||||
|
||||
* Dot notation for objects, hashes and arrays
|
||||
|
||||
* Use expressions without any disadvantages like those in the
|
||||
HTML::Template::Expr manpage
|
||||
|
||||
* Write escaping plugins and plugins for new tags
|
||||
|
||||
* Alternate delimiters, e.g. '[%if %]' and '<%if %>'
|
||||
|
||||
* Avoid 'global_vars' option by using the 'SET_VAR' tag to create aliases.
|
||||
|
||||
* Tags ELSIF, EACH, WHILE, COMMENT, WRAPPER, SWITCH/CASE, INCLUDE_VAR
|
||||
|
||||
* Chomp newlines/whitespace
|
||||
|
||||
For a quick reference, see the HTML::Template::Compiled::Reference manpage.
|
||||
|
||||
As the basic features work like in the HTML::Template manpage, please get
|
||||
familiar with this documentation before.
|
||||
familiar with its documentation before.
|
||||
|
||||
HTML::Template::Compiled (HTC) does not implement all features of the
|
||||
HTML::Template manpage, and it has got some additional features which are
|
||||
explained below: the "ADDITIONAL FEATURES" manpage
|
||||
HTML::Template manpage (see the "COMPATIBILITY" manpage), and it has got
|
||||
some additional features which are explained below: the "ADDITIONAL
|
||||
FEATURES" manpage
|
||||
|
||||
HTML::Template::Compiled (HTC) is a template system which uses the same
|
||||
template syntax as HTML::Template and the same perl API (see the
|
||||
"COMPATIBILITY" manpage for what you need to know if you want (almost) the
|
||||
same behaviour). Internally it works different, because it turns the
|
||||
template into perl code, and once that is done, generating the output is
|
||||
much faster than with HTML::Template (3-7 times at the moment, depending on
|
||||
the options you use (see the "BENCHMARKS" manpage for some examples), when
|
||||
both are run with loop_context_vars 0. It also can generate perl files so
|
||||
that the next time the template is loaded it doesn't have to be parsed
|
||||
again. The best performance gain is probably reached in applications
|
||||
running under mod_perl, for example.
|
||||
|
||||
If you don't use any caching HTC will be very slow, slower than TT. Also
|
||||
with file caching but without memory caching it's the slowest templating
|
||||
module I know. With memory caching, though, it is one of the fastest, even
|
||||
faster sometimes (depending on options and template size) than C modules.
|
||||
See the "BENCHMARKS" manpage for some examples on the performance. Since it
|
||||
depends highly on the options used and on the template size there can be no
|
||||
general statement on its performance.
|
||||
|
||||
You might want to use the HTML::Template::Compiled::Lazy manpage for CGI
|
||||
environments as it doesn't parse the template before calling output. But
|
||||
@@ -70,7 +87,7 @@ memory. If you are on mod_perl, and have a lot of templates, you should
|
||||
preload them at server startup to be sure that it is in shared memory. At
|
||||
the moment HTC is not fully tested for keeping all data in shared memory
|
||||
(e.g. when a copy-on-write occurs), but it seems like it's behaving well.
|
||||
For preloading you can now use HTML::Template::Compiled->preload($dir).
|
||||
For preloading you can use HTML::Template::Compiled->preload($cache_dir).
|
||||
|
||||
Generating code, writing it on disk and later eval() it can open security
|
||||
holes, for example if you have more users on the same machine that can
|
||||
@@ -102,9 +119,6 @@ passing for HTC. See the "RESOURCES" manpage for current information.
|
||||
./Build install destdir=%{buildroot} create_packlist=0
|
||||
%perl_gen_filelist
|
||||
|
||||
%clean
|
||||
%{__rm} -rf %{buildroot}
|
||||
|
||||
%files -f %{name}.files
|
||||
%defattr(-,root,root,755)
|
||||
%doc Changes examples README
|
||||
|
Reference in New Issue
Block a user