debian/control: update {versioned,alternative} (build) dependencies.
gregor herrmann
11 years ago
0 | 0 | Source: libfile-policy-perl |
1 | Maintainer: Debian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org> | |
2 | Uploaders: AGOSTINI Yves <agostini@univ-metz.fr> | |
1 | 3 | Section: perl |
2 | 4 | Priority: optional |
3 | 5 | Build-Depends: debhelper (>= 5) |
4 | Build-Depends-Indep: perl (>= 5.6.10-12),libtest-pod-perl, libtest-pod-coverage-perl, libtest-assertions-perl, liblog-trace-perl, libfile-slurp-perl | |
5 | Maintainer: Debian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org> | |
6 | Uploaders: AGOSTINI Yves <agostini@univ-metz.fr> | |
6 | Build-Depends-Indep: perl, | |
7 | libtest-pod-perl, | |
8 | libtest-pod-coverage-perl, | |
9 | libtest-assertions-perl, | |
10 | liblog-trace-perl, | |
11 | libfile-slurp-perl | |
7 | 12 | Standards-Version: 3.7.3 |
13 | Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libfile-policy-perl.git | |
14 | Vcs-Git: git://git.debian.org/pkg-perl/packages/libfile-policy-perl.git | |
8 | 15 | Homepage: http://search.cpan.org/dist/File-Policy/ |
9 | Vcs-Git: git://git.debian.org/pkg-perl/packages/libfile-policy-perl.git | |
10 | Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libfile-policy-perl.git | |
11 | 16 | |
12 | 17 | Package: libfile-policy-perl |
13 | 18 | Architecture: all |
14 | Depends: ${perl:Depends}, ${misc:Depends}, libtest-assertions-perl, liblog-trace-perl, libfile-slurp-perl | |
15 | Description: Simple policy for file I/O functions | |
19 | Depends: ${perl:Depends}, | |
20 | ${misc:Depends}, | |
21 | libtest-assertions-perl, | |
22 | liblog-trace-perl, | |
23 | libfile-slurp-perl | |
24 | Description: Simple policy for file I/O functions | |
16 | 25 | This defines the policy for file I/O with modules such as |
17 | 26 | File::Slurp::WithinPolicy. The purpose is to allow systems administrators to |
18 | 27 | define locations and restrictions for applications' file I/O and give app |
34 | 43 | other people. Simply ensuring that submitted code calls check_safe() ensures |
35 | 44 | file access is sane, reducing the amount of effort required to do a security |
36 | 45 | audit. |
46 |