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
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
|
Source: dbconfig-common
Section: admin
Priority: optional
Maintainer: Paul Gevers <elbrus@debian.org>
Build-Depends:
debhelper-compat (= 12),
debiandoc-sgml,
dpkg (>= 1.17.11),
ghostscript,
po-debconf,
texlive-fonts-recommended,
texlive-latex-extra,
texlive-latex-recommended
Standards-Version: 4.2.1
Rules-Requires-Root: no
Vcs-Git: https://salsa.debian.org/debian/dbconfig-common.git
Vcs-Browser: https://salsa.debian.org/debian/dbconfig-common
Package: dbconfig-common
Architecture: all
Depends:
ucf,
${misc:Depends}
Suggests:
dbconfig-mysql | dbconfig-pgsql | dbconfig-sqlite3 | dbconfig-no-thanks
Breaks:
bandwidthd-pgsql (<< 2.0.1+cvs20090917-9~)
Description: framework that helps packages to manage databases
This package contains the core of the dbconfig-common framework. This
framework presents a policy and implementation for managing various databases
used by applications included in Debian packages.
.
It can:
- support MySQL/MariaDB, PostgreSQL, and SQLite3 based applications;
- create or remove databases and database users;
- access local or remote databases;
- upgrade/modify databases when upstream changes database structure;
- generate config files in many formats with the database info;
- import configs from packages previously managing databases on their own;
- prompt users with a set of normalized, pre-translated questions;
- handle failures gracefully, with an option to retry;
- do all the hard work automatically;
- work for package maintainers with little effort on their part;
- work for local admins with little effort on their part;
- comply with an agreed upon set of standards for behavior;
- do absolutely nothing if that is the whim of the local admin;
- perform all operations from within the standard flow of
package management (no additional skill is required of the local
admin).
Package: dbconfig-mysql
Architecture: all
Depends:
dbconfig-common (>= 2),
default-mysql-client | virtual-mysql-client,
${misc:Depends}
Suggests:
default-mysql-server | virtual-mysql-server
Conflicts:
dbconfig-no-thanks
Description: dbconfig-common MySQL/MariaDB support
This package ensures MySQL/MariaDB support in the dbconfig-common framework,
and should be in the depends list of packages that require MySQL support from
dbconfig-common.
.
System administrators that don't want dbconfig-common to handle the database
management should install dbconfig-no-thanks instead.
Package: dbconfig-pgsql
Architecture: all
Depends:
dbconfig-common (>= 2),
postgresql-client,
${misc:Depends}
Suggests:
postgresql
Conflicts:
dbconfig-no-thanks
Description: dbconfig-common PostgreSQL support
This package ensures PostgreSQL support in the dbconfig-common framework, and
should be in the depends list of packages that require PostgreSQL support from
dbconfig-common.
.
System administrators that don't want dbconfig-common to handle the database
management should install dbconfig-no-thanks instead.
Package: dbconfig-sqlite3
Architecture: all
Depends:
dbconfig-common (>= 2),
sqlite3,
${misc:Depends}
Conflicts:
dbconfig-no-thanks
Description: dbconfig-common SQLite3 support
This package ensures SQLite3 support in the dbconfig-common framework, and
should be in the depends list of packages that require SQLite3 support from
dbconfig-common.
.
System administrators that don't want dbconfig-common to handle the database
management should install dbconfig-no-thanks instead.
Package: dbconfig-no-thanks
Architecture: all
Depends:
dbconfig-common (>= 2),
${misc:Depends}
Conflicts:
dbconfig-mysql,
dbconfig-pgsql,
dbconfig-sqlite,
dbconfig-sqlite3
Description: dbconfig-common bypass
If a package relies on the dbconfig-common framework for database setup and
maintenance, installing dbconfig-no-thanks instead of one of dbconfig's
database-specific packages will block this function. It is intended for cases
where the system administrator desires or requires full control of the
database or where dbconfig-common makes bad choices, and typically leaves
the depending packages non-functional until manually configured.
|
