source: trunk/debathena/third/schroot/debian/control @ 24168

Revision 24168, 7.9 KB checked in by broder, 15 years ago (diff)
Adjust schroot build-deps for backport to Jaunty.
Line 
1Source: schroot
2Section: admin
3Priority: optional
4Maintainer: Debian buildd-tools Developers <buildd-tools-devel@lists.alioth.debian.org>
5Uploaders: Michael Banck <mbanck@debian.org>, Luk Claes <luk@debian.org>, Roger Leigh <rleigh@debian.org>, Francesco Paolo Lovergine <frankie@debian.org>
6Build-Depends: debhelper (>= 7.0.0), autotools-dev, pkg-config (>= 0.20), libpam0g-dev (>= 0.79-3.1), uuid-dev, liblockdev1-dev (>= 1.0.2), libboost1.37-dev (>= 1.37.0), libboost-program-options1.37-dev (>= 1.37.0), libboost-regex1.37-dev (>= 1.37.0), libboost-filesystem1.37-dev (>= 1.37.0), gettext, libcppunit-dev, doxygen, graphviz
7Standards-Version: 3.8.3
8Vcs-Browser: http://git.debian.org/?p=buildd-tools/schroot.git
9Vcs-Git: git://git.debian.org/git/buildd-tools/schroot
10
11Package: schroot-common
12Architecture: all
13Replaces: schroot (<< 1.1.1)
14Description: common files for schroot
15 schroot allows users to execute commands or interactive shells in
16 different chroots.  Any number of named chroots may be created, and
17 access permissions given to each, including root access for normal
18 users, on a per-user or per-group basis.  Additionally, schroot can
19 switch to a different user in the chroot, using PAM for
20 authentication and authorisation.  All operations are logged for
21 security.
22 .
23 This package provides translations for localisation of schroot
24 programs.
25
26Package: libsbuild-dev
27Architecture: any
28Section: libdevel
29Depends: pkg-config (>= 0.14.0)
30Suggests: schroot-dbg, libsbuild-doc
31Description: development files for the Debian source builder
32 sbuild provides facilities to manage and access chroots, as part of
33 schroot.
34 .
35 schroot allows users to execute commands or interactive shells in
36 different chroots.  Any number of named chroots may be created, and
37 access permissions given to each, including root access for normal
38 users, on a per-user or per-group basis.  Additionally, schroot can
39 switch to a different user in the chroot, using PAM for
40 authentication and authorisation.  All operations are logged for
41 security.
42 .
43 This package contains the header files and static library needed to
44 develop applications which make use of sbuild.  Once the API and ABI
45 are stable, a shared library will replace the static library.
46
47Package: schroot-dbg
48Architecture: any
49Section: debug
50Priority: extra
51Depends: schroot (= ${binary:Version}) | dchroot (= ${binary:Version})
52 | dchroot-dsa (= ${binary:Version})
53Conflicts: schroot (<< ${binary:Version}), schroot (>> ${binary:Version}),
54 dchroot (<< ${binary:Version}), dchroot (>>${binary:Version}),
55 dchroot-dsa (<< ${binary:Version}), dchroot-dsa (>>${binary:Version})
56Description: schroot, dchroot and dchroot-dsa debuggging symbols
57 sbuild provides facilities to manage and access chroots, as part of
58 schroot.
59 .
60 schroot allows users to execute commands or interactive shells in
61 different chroots.  Any number of named chroots may be created, and
62 access permissions given to each, including root access for normal
63 users, on a per-user or per-group basis.  Additionally, schroot can
64 switch to a different user in the chroot, using PAM for
65 authentication and authorisation.  All operations are logged for
66 security.
67 .
68 This package contains debugging symbols for the schroot, dchroot
69 and dchroot-dsa packages.
70
71Package: libsbuild-doc
72Architecture: all
73Section: doc
74Suggests: libsbuild-dev
75Description: development documentation for the Debian source builder
76 sbuild provides facilities to manage and access chroots, as part of
77 schroot.
78 .
79 schroot allows users to execute commands or interactive shells in
80 different chroots.  Any number of named chroots may be created, and
81 access permissions given to each, including root access for normal
82 users, on a per-user or per-group basis.  Additionally, schroot can
83 switch to a different user in the chroot, using PAM for
84 authentication and authorisation.  All operations are logged for
85 security.
86 .
87 This package contains the API documentation needed to develop
88 applications which make use of sbuild.
89
90Package: schroot
91Architecture: any
92Depends: ${shlibs:Depends}, schroot-common (=${source:Version})
93Conflicts: dchroot (<< 0.13)
94Enhances: sbuild
95Suggests: debootstrap, lvm2, unzip, aufs-modules | unionfs-modules
96Description: Execute commands in a chroot environment
97 schroot allows users to execute commands or interactive shells in
98 different chroots.  Any number of named chroots may be created, and
99 access permissions given to each, including root access for normal
100 users, on a per-user or per-group basis.  Additionally, schroot can
101 switch to a different user in the chroot, using PAM for
102 authentication and authorisation.  All operations are logged for
103 security.
104 .
105 Several different types of chroot are supported, including normal
106 directories in the filesystem, and also block devices.  Sessions,
107 persistent chroots created on the fly from files (tar with optional
108 compression and zip) and LVM snapshots are also supported.
109 .
110 schroot supports kernel personalities, allowing the programs run
111 inside the chroot to have a different personality.  For example,
112 running 32-bit chroots on 64-bit systems, or even running binaries
113 from alternative operating systems such as SVR4 or Xenix.
114 .
115 schroot also integrates with sbuild, to allow building packages with
116 all supported chroot types, including session-managed chroot types
117 such as LVM snapshots.
118 .
119 schroot shares most of its options with dchroot, but offers vastly
120 more functionality.
121
122Package: dchroot
123Architecture: any
124Suggests: debootstrap
125Depends: schroot (= ${binary:Version}), ${shlibs:Depends}, schroot-common (=${source:Version})
126Description: Execute commands in a chroot environment
127 dchroot allows users to execute commands or interactive shells in
128 different chroots.  A typical installation might provide 'stable',
129 'testing' and 'unstable' chroots.  Users can move between chroots as
130 necessary.
131 .
132 NOTE: the schroot package provides a better implementation of
133 dchroot.  In particular:
134  * dchroot quoting issues are not present.  dchroot runs commands in
135    the chroot with -c option of the user's default shell; when
136    multiple command options are used, the options are concatenated
137    together, separated by spaces.  This concatenation breaks shell
138    quoting.
139  * schroot implements fine-grained access controls based on users
140    and groups, either of which may be granted the ability to gain
141    root access to the chroot if required.
142 Using schroot will avoid these issues, as well as provide additional
143 functionality dchroot does not possess.
144
145Package: dchroot-dsa
146Architecture: any
147Suggests: debootstrap
148Depends: schroot (= ${binary:Version}), ${shlibs:Depends}, schroot-common (=${source:Version})
149Description: Execute commands in a chroot environment
150 dchroot allows users to execute commands or interactive shells in
151 different chroots.  A typical installation might provide 'stable',
152 'testing' and 'unstable' chroots.  Users can move between chroots as
153 necessary.
154 .
155 This package provides a dchroot-dsa binary which is compatible with
156 the command-line options and configuration file format used by the
157 dchroot-dsa dchroot maintained by the Debian System Administrators
158 used on machines administered for the Debian Project.
159 .
160 NOTE: the schroot package provides a better implementation of
161 dchroot-dsa.  In particular:
162  * dchroot-dsa only allows the specification of a single command with
163    an absolute path, and no options may be used with the command;
164    schroot allows the use of relative and absolute paths with no
165    limit on the number of options.
166  * dchroot-dsa only allows one chroot to be used at once; schroot will
167    allow the use of as many chroots as desired.
168  * dchroot-dsa allows access to be restricted to named users; schroot
169    implements finer-grained access controls based on users and groups,
170    either of which may be granted the ability to gain root access to
171    the chroot if required.
172 Using schroot will avoid these issues, as well as provide significant
173 additional functionality dchroot-dsa does not possess.
Note: See TracBrowser for help on using the repository browser.