# HG changeset patch
# User Hans-G?nter Theisgen
# Date 1641113677 -3600
# Node ID 3026aad208f2ad2c0cf4b987fca38ed32975ce74
# Parent  9645753904c820f0aff4388b740d63a2d8a6608d
updated perl-template-toolkit (3.008 -> 3.010)

diff -r 9645753904c8 -r 3026aad208f2 perl-template-toolkit/description.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/perl-template-toolkit/description.txt	Sun Jan 02 09:54:37 2022 +0100
@@ -0,0 +1,34 @@
+The Template Toolkit is a collection of Perl modules which implement a fast,
+flexible, powerful and extensible template processing system.
+
+It is "input-agnostic" and can be used equally well for processing any kind
+of text documents: HTML, XML, CSS, Javascript, Perl code, plain text,
+and so on.
+However, it is most often used for generating static and dynamic web content,
+so that's what we'll focus on here.
+
+Although the Template Toolkit is written in Perl, you don't need to be a Perl
+programmer to use it. It was designed to allow non-programmers to easily
+create and maintain template-based web sites without having to mess around
+writing Perl code or going crazy with cut-n-paste.
+
+However, the Template Toolkit is also designed to be extremely flexible and
+extensible. If you are a Perl programmer, or know someone who is, then you
+can easily hook the Template Toolkit into your existing code, data, databases
+and web applications.
+Furthermore, you can easily extend the Template Toolkit through the use of
+its plugin mechanism and other developer APIs.
+
+Whatever context you use it in, the primary purpose of the Template Toolkit
+is to allow you to create a clear separation between the presentation elements
+of your web site and everything else.
+
+If you're generating static web pages, then you can use it to separate the
+commonly repeated user interface elements on each page (headers, menus,
+footers, etc.) from the core content.
+If you're generating dynamic web pages for the front end of a web application,
+then you'll also be using it to keep the back-end Perl code entirely separate
+from the front-end HTML templates.
+Either way, a clear separation of concerns is what allow you to concentrate
+on one thing at a time without the other things getting in your way.
+And that's what the Template Toolkit is all about.
diff -r 9645753904c8 -r 3026aad208f2 perl-template-toolkit/receipt
--- a/perl-template-toolkit/receipt	Sun Jan 02 09:51:29 2022 +0100
+++ b/perl-template-toolkit/receipt	Sun Jan 02 09:54:37 2022 +0100
@@ -1,19 +1,20 @@
 # SliTaz package receipt.
 
 PACKAGE="perl-template-toolkit"
-VERSION="3.008"
+VERSION="3.010"
 CATEGORY="development"
 SHORT_DESC="Perl Module Template Toolkit."
 MAINTAINER="nneul@neulinger.org"
-LICENSE="Artistic"
-WEB_SITE="https://metacpan.org/release/Template-Toolkit/"
+LICENSE="GPL"
+WEB_SITE="https://metacpan.org/pod/Template::Toolkit"
+REPOLOGY="perl:template-toolkit"
 
 SOURCE="Template-Toolkit"
 TARBALL="$SOURCE-$VERSION.tar.gz"
 WGET_URL="https://www.cpan.org/modules/by-module/Template/$TARBALL"
 
 DEPENDS="perl perl-appconfig"
-BUILD_DEPENDS="perl-appconfig"
+BUILD_DEPENDS="perl perl-appconfig"
 
 current_version()
 {
@@ -26,16 +27,14 @@
 {
 	perl Makefile.PL TT_XS_ENABLE=y TT_XS_DEFAULT=y TT_ACCEPT=y TT_QUIET=n &&
 	make && 
-	make DESTDIR=$DESTDIR install
+	make install DESTDIR=$DESTDIR
 }
 
 # Rules to gen a SliTaz package suitable for Tazpkg.
 genpkg_rules()
 {
-	mkdir -p $fs/usr
-	cp -a $install/usr/lib	$fs/usr
-
+	cook_copy_folders	lib
 	# remove perllocal.pod and .packlist
-	find $fs -name perllocal.pod -delete
-	find $fs -name .packlist -delete
+	find ${fs} -name perllocal.pod -delete
+	find ${fs} -name .packlist -delete
 }