Debian Codegraph @

debian/control

raw
1 Source: python-pbr
2 Section: python
3 Priority: optional
4 Maintainer: Debian OpenStack <[email protected]>
5 Uploaders:
6 Thomas Goirand <[email protected]>,
7 Prach Pongpanich <[email protected]>,
8 Build-Depends:
9 debhelper-compat (= 10),
10 dh-python,
11 git,
12 gnupg,
13 openstack-pkg-tools,
14 python3-all,
15 python3-setuptools,
16 python3-sphinx <!nodoc>,
17 Build-Depends-Indep:
18 python3-all-dev <!nocheck>,
19 python3-coverage <!nocheck>,
20 python3-fixtures <!nocheck>,
21 python3-markupsafe <!nocheck>,
22 python3-openstackdocstheme <!nocheck>,
23 python3-packaging,
24 python3-pip <!nocheck>,
25 python3-reno <!nodoc>,
26 python3-sphinxcontrib.apidoc <!nodoc>,
27 python3-stestr <!nocheck>,
28 python3-testresources <!nocheck>,
29 python3-testscenarios <!nocheck>,
30 python3-testtools <!nocheck>,
31 python3-virtualenv (>= 20.0) <!nocheck>,
32 python3-wheel <!nocheck>,
33 subunit <!nocheck>,
34 Standards-Version: 4.4.1
35 Rules-Requires-Root: no
36 Vcs-Browser: https://salsa.debian.org/openstack-team/libs/python-pbr
37 Vcs-Git: https://salsa.debian.org/openstack-team/libs/python-pbr.git
38 Homepage: https://pypi.python.org/pypi/pbr
39
40 Package: python-pbr-doc
41 Section: doc
42 Architecture: all
43 Multi-Arch: foreign
44 Depends:
45 ${misc:Depends},
46 ${sphinxdoc:Depends},
47 Description: inject useful and sensible default behaviors into setuptools - doc
48 PBR (Python Build Reasonableness) is a library that injects some useful and
49 sensible default behaviors into your setuptools run. PBR can:
50 * Manage version number based on git revisions and tags (Version file).
51 * Generate AUTHORS file from git log
52 * Generate ChangeLog from git log
53 * Generate Sphinx autodoc stub files for your whole module
54 * Store your dependencies in a pip requirements file
55 * Use your README file as a long_description
56 * Smartly find packages under your root package
57 .
58 PBR is only mildly configurable. The basic idea is that there's a decent way
59 to run things and if you do, you should reap the rewards, because then it's
60 simple and repeatable. If you want to do things differently, cool! But you've
61 already got the power of Python at your fingertips, so you don't really need
62 PBR.
63 .
64 PBR builds on top of the work that d2to1 started to provide for declarative
65 configuration. d2to1 is itself an implementation of the ideas behind
66 distutils2. Although distutils2 is now abandoned in favor of work towards PEP
67 426 and Metadata 2.0, declarative config is still a great idea and
68 specifically important in trying to distribute setup code as a library when
69 that library itself will alter how the setup is processed. As Metadata 2.0 and
70 other modern Python packaging PEPs come out, PBR aims to support them as
71 quickly as possible.
72 .
73 This package provides the documentation.
74
75 Package: python3-pbr
76 Architecture: all
77 Depends:
78 python3-setuptools,
79 ${misc:Depends},
80 ${python3:Depends},
81 Recommends:
82 ${python3:Recommends},
83 Description: inject useful and sensible default behaviors into setuptools - Python 3.x
84 PBR (Python Build Reasonableness) is a library that injects some useful and
85 sensible default behaviors into your setuptools run. PBR can:
86 * Manage version number based on git revisions and tags (Version file).
87 * Generate AUTHORS file from git log
88 * Generate ChangeLog from git log
89 * Generate Sphinx autodoc stub files for your whole module
90 * Store your dependencies in a pip requirements file
91 * Use your README file as a long_description
92 * Smartly find packages under your root package
93 .
94 PBR is only mildly configurable. The basic idea is that there's a decent way
95 to run things and if you do, you should reap the rewards, because then it's
96 simple and repeatable. If you want to do things differently, cool! But you've
97 already got the power of Python at your fingertips, so you don't really need
98 PBR.
99 .
100 PBR builds on top of the work that d2to1 started to provide for declarative
101 configuration. d2to1 is itself an implementation of the ideas behind
102 distutils2. Although distutils2 is now abandoned in favor of work towards PEP
103 426 and Metadata 2.0, declarative config is still a great idea and
104 specifically important in trying to distribute setup code as a library when
105 that library itself will alter how the setup is processed. As Metadata 2.0 and
106 other modern Python packaging PEPs come out, PBR aims to support them as
107 quickly as possible.
108 .
109 This package provides support for Python 3.x.