File: control

package info (click to toggle)
activeldap 1.2.2-1
  • links: PTS, VCS
  • area: main
  • in suites: squeeze
  • size: 6,732 kB
  • ctags: 4,523
  • sloc: ruby: 27,236; makefile: 11; sh: 1
file content (44 lines) | stat: -rw-r--r-- 1,901 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
Source: activeldap
Section: ruby
Priority: optional
Maintainer: Marc Dequènes (Duck) <Duck@DuckCorp.org>
DM-Upload-Allowed: yes
Uploaders: Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>, 
	   Deepak Tripathi <apenguinlinux@gmail.com>
Build-Depends: cdbs (>= 0.4.53),
 debhelper (>= 7.0.1), ruby (>= 1.8.1), ruby-pkg-tools (>= 0.8)
Build-Depends-Indep: graphviz
Vcs-Svn: svn://svn.debian.org/svn/pkg-ruby-extras/trunk/activeldap/
Vcs-Browser: http://svn.debian.org/viewsvn/pkg-ruby-extras/trunk/activeldap/
Standards-Version: 3.9.0
Homepage: http://rubyforge.org/projects/ruby-activeldap

Package: libactiveldap-ruby
Architecture: all
Depends: ${misc:Depends}, libactiveldap-ruby1.8
Description: an object-oriented interface to LDAP for Ruby
 This is a dependency package, which depends on an ActiveLDAP package
 built for the latest version of Ruby.

Package: libactiveldap-ruby-doc
Section: doc
Architecture: all
Depends: ${misc:Depends}
Suggests: doc-base, libjs-prototype
Description: an object-oriented interface to LDAP for Ruby
 This is the Rdoc-generated documentation for ActiveLDAP API.

Package: libactiveldap-ruby1.8
Architecture: all
Depends: ${misc:Depends}, libruby1.8, libldap-ruby1.8 (>= 0.8.2), libactivesupport-ruby1.8 (>= 2.3.5), libactiverecord-ruby1.8 (>= 2.3.5), liblocale-ruby1.8 (>= 2.0.5), libgettext-activerecord-ruby1.8 (>= 2.1.0)
Suggests: liblog4r-ruby1.8 (>= 1.0.4)
Description: an object-oriented interface to LDAP for Ruby
 ActiveLDAP is a wrapper around Ruby/LDAP with its interface inspired
 by ActiveRecord (from the Rails project).
 .
 It dynamically parses the LDAP server’s schema based on the
 objectClasses an entry has. It then exposes the LDAP attributes as
 methods on the object. This means that if you update the objectClass
 on an object, the methods/attributes available for changing are
 automatically updated.