File: control

package info (click to toggle)
resmgr 1.0-2sarge2
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 308 kB
  • ctags: 313
  • sloc: ansic: 3,165; sh: 556; makefile: 109
file content (49 lines) | stat: -rw-r--r-- 1,741 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
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
Source: resmgr
Section: admin
Priority: optional
Maintainer: Julien BLACHE <jblache@debian.org>
Build-Depends: debhelper (>= 4.0.0), dpatch, libpam0g-dev
Standards-Version: 3.6.1

Package: libresmgr-dev
Section: libdevel
Architecture: any
Depends: libresmgr1 (= ${Source-Version})
Description: resource manager library [development files]
 The resource manager library was designed to ease the use of device
 nodes in desktop setups, where users should be able to access e.g.
 scanners, CD or DVD burners, etc.
 .
 Using a PAM module and a helper daemon, it acts as a proxy between
 the applications and the actual devices, by-passing permissions problems
 easily and elegantly.

Package: libresmgr1
Section: libs
Architecture: any
Depends: ${shlibs:Depends}
Recommends: resmgr
Description: resource manager library
 The resource manager library was designed to ease the use of device
 nodes in desktop setups, where users should be able to access e.g.
 scanners, CD or DVD burners, etc.
 .
 Using a PAM module and a helper daemon, it acts as a proxy between
 the applications and the actual devices, by-passing permissions problems
 easily and elegantly.
 .
 libresmgr can be integrated with hotplug to add and remove devices
 on-the-fly.

Package: resmgr
Section: admin
Architecture: any
Depends: ${shlibs:Depends}
Description: resource manager library daemon and PAM module
 resmgrd is the daemon accompanying libresmgr, the resource manager
 library. This package also contains the PAM module and the resmgr
 command-line client needed to make full use of resmgr.
 .
 The resmgrd daemon is responsible for checking the resource management
 policy of the system and then acting as a proxy between the application
 and the actual devices.