wok rev 24253
updated perl-template-toolkit (3.008 -> 3.010)
author | Hans-G?nter Theisgen |
---|---|
date | Sun Jan 02 09:54:37 2022 +0100 (2022-01-02) |
parents | 9645753904c8 |
children | 5376bbd57905 |
files | perl-template-toolkit/description.txt perl-template-toolkit/receipt |
line diff
1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000 1.2 +++ b/perl-template-toolkit/description.txt Sun Jan 02 09:54:37 2022 +0100 1.3 @@ -0,0 +1,34 @@ 1.4 +The Template Toolkit is a collection of Perl modules which implement a fast, 1.5 +flexible, powerful and extensible template processing system. 1.6 + 1.7 +It is "input-agnostic" and can be used equally well for processing any kind 1.8 +of text documents: HTML, XML, CSS, Javascript, Perl code, plain text, 1.9 +and so on. 1.10 +However, it is most often used for generating static and dynamic web content, 1.11 +so that's what we'll focus on here. 1.12 + 1.13 +Although the Template Toolkit is written in Perl, you don't need to be a Perl 1.14 +programmer to use it. It was designed to allow non-programmers to easily 1.15 +create and maintain template-based web sites without having to mess around 1.16 +writing Perl code or going crazy with cut-n-paste. 1.17 + 1.18 +However, the Template Toolkit is also designed to be extremely flexible and 1.19 +extensible. If you are a Perl programmer, or know someone who is, then you 1.20 +can easily hook the Template Toolkit into your existing code, data, databases 1.21 +and web applications. 1.22 +Furthermore, you can easily extend the Template Toolkit through the use of 1.23 +its plugin mechanism and other developer APIs. 1.24 + 1.25 +Whatever context you use it in, the primary purpose of the Template Toolkit 1.26 +is to allow you to create a clear separation between the presentation elements 1.27 +of your web site and everything else. 1.28 + 1.29 +If you're generating static web pages, then you can use it to separate the 1.30 +commonly repeated user interface elements on each page (headers, menus, 1.31 +footers, etc.) from the core content. 1.32 +If you're generating dynamic web pages for the front end of a web application, 1.33 +then you'll also be using it to keep the back-end Perl code entirely separate 1.34 +from the front-end HTML templates. 1.35 +Either way, a clear separation of concerns is what allow you to concentrate 1.36 +on one thing at a time without the other things getting in your way. 1.37 +And that's what the Template Toolkit is all about.
2.1 --- a/perl-template-toolkit/receipt Sun Jan 02 09:51:29 2022 +0100 2.2 +++ b/perl-template-toolkit/receipt Sun Jan 02 09:54:37 2022 +0100 2.3 @@ -1,19 +1,20 @@ 2.4 # SliTaz package receipt. 2.5 2.6 PACKAGE="perl-template-toolkit" 2.7 -VERSION="3.008" 2.8 +VERSION="3.010" 2.9 CATEGORY="development" 2.10 SHORT_DESC="Perl Module Template Toolkit." 2.11 MAINTAINER="nneul@neulinger.org" 2.12 -LICENSE="Artistic" 2.13 -WEB_SITE="https://metacpan.org/release/Template-Toolkit/" 2.14 +LICENSE="GPL" 2.15 +WEB_SITE="https://metacpan.org/pod/Template::Toolkit" 2.16 +REPOLOGY="perl:template-toolkit" 2.17 2.18 SOURCE="Template-Toolkit" 2.19 TARBALL="$SOURCE-$VERSION.tar.gz" 2.20 WGET_URL="https://www.cpan.org/modules/by-module/Template/$TARBALL" 2.21 2.22 DEPENDS="perl perl-appconfig" 2.23 -BUILD_DEPENDS="perl-appconfig" 2.24 +BUILD_DEPENDS="perl perl-appconfig" 2.25 2.26 current_version() 2.27 { 2.28 @@ -26,16 +27,14 @@ 2.29 { 2.30 perl Makefile.PL TT_XS_ENABLE=y TT_XS_DEFAULT=y TT_ACCEPT=y TT_QUIET=n && 2.31 make && 2.32 - make DESTDIR=$DESTDIR install 2.33 + make install DESTDIR=$DESTDIR 2.34 } 2.35 2.36 # Rules to gen a SliTaz package suitable for Tazpkg. 2.37 genpkg_rules() 2.38 { 2.39 - mkdir -p $fs/usr 2.40 - cp -a $install/usr/lib $fs/usr 2.41 - 2.42 + cook_copy_folders lib 2.43 # remove perllocal.pod and .packlist 2.44 - find $fs -name perllocal.pod -delete 2.45 - find $fs -name .packlist -delete 2.46 + find ${fs} -name perllocal.pod -delete 2.47 + find ${fs} -name .packlist -delete 2.48 }