File: control

package info (click to toggle)
libclass-dbi-fromcgi-perl 1.00-5
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 100 kB
  • sloc: perl: 279; makefile: 2
file content (43 lines) | stat: -rw-r--r-- 1,941 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
Source: libclass-dbi-fromcgi-perl
Maintainer: Debian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org>
Uploaders: Ansgar Burchardt <ansgar@debian.org>
Section: perl
Priority: optional
Build-Depends: debhelper (>= 11)
Build-Depends-Indep: perl,
                     libclass-dbi-perl,
                     libcgi-untaint-perl,
                     libtest-pod-perl,
                     libtest-pod-coverage-perl,
                     libdbd-sqlite3-perl,
                     libclass-dbi-sqlite-perl
Standards-Version: 4.1.4
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libclass-dbi-fromcgi-perl
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libclass-dbi-fromcgi-perl.git
Homepage: https://metacpan.org/release/Class-DBI-FromCGI
Testsuite: autopkgtest-pkg-perl

Package: libclass-dbi-fromcgi-perl
Architecture: all
Depends: ${misc:Depends},
         ${perl:Depends},
         libclass-dbi-perl,
         libcgi-untaint-perl
Description: Perl module to update Class::DBI data using CGI::Untaint
 Lots of times, Class::DBI is used in web-based applications. (In
 fact, coupled with a templating system that allows you to pass
 objects, such as Template::Toolkit, Class::DBI is very much your
 friend for these.)
 .
 One of the most irritating things about writing web-based applications
 is the monotony of writing much of the same stuff over and over again.
 And, where there's monotony there's a tendency to skip over stuff that
 is really important, but is a pain to write - like Taint Checking and
 sensible input validation. (Especially as you can still show a 'working'
 application without it!). CGI::Untaint can take care of a lot of that
 for us.
 .
 It so happens that CGI::Untaint also plays well with Class::DBI. All
 you need to do is to 'use Class::DBI::FromCGI' in your class (or in
 your local Class::DBI subclass that all your other classes inherit
 from. You do that, don't you?).