File: control

package info (click to toggle)
env-assert 0.011-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 268 kB
  • sloc: perl: 455; makefile: 2
file content (34 lines) | stat: -rw-r--r-- 1,271 bytes parent folder | download
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
Source: env-assert
Standards-Version: 4.7.2
Maintainer: Debian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org>
Uploaders:
 gregor herrmann <gregoa@debian.org>,
Section: utils
Testsuite: autopkgtest-pkg-perl
Build-Depends:
 debhelper-compat (= 13),
Build-Depends-Indep:
 libtest2-suite-perl <!nocheck>,
 perl,
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/env-assert
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/env-assert.git
Homepage: https://metacpan.org/release/Env-Assert

Package: env-assert
Architecture: all
Depends:
 ${misc:Depends},
 ${perl:Depends},
Description: tool to ensure that the environment variables match expectations
 The envassert script, accompanied by the Env::Assert module, checks that
 your runtime environment, as defined with environment variables, matches with
 what you want.
 .
 You can define your required environment in a file.
 Default file is .envassert but you can use any file.
 .
 It is advantageous to use envassert for examnple when running a container. If
 you check your environment for missing or wrongly defined environment
 variables at the beginning of the container run, your container will fail
 sooner instead of in a later point in execution when the variables are
 needed.