File: control

package info (click to toggle)
evolution 1.0.5-1woody2
  • links: PTS
  • area: main
  • in suites: woody
  • size: 14,876 kB
  • ctags: 22
  • sloc: sh: 292; makefile: 217
file content (52 lines) | stat: -rw-r--r-- 2,106 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
50
51
52
Source: evolution
Section: mail
Priority: optional
Maintainer: Takuo KITAME <kitame@northeye.org>
Build-Depends: imlib-dev, bison, byacc, flex, autoconf, intltool, libtool, debhelper (>> 3.0.0), libgal-dev (>= 0.19), gtkhtml (>= 1.0.2), libgtkhtml-dev (>= 1.0.2), libbonobo-dev (>= 1.0.19), libldap2-dev, libgnome-vfs-dev (>= 1.0.5), bonobo-conf (>= 0.14), libbonobo-conf-dev (>= 0.14), libnss-dev (>= 2:0.9.9), scrollkeeper, libsasl-dev, libgnome-pilot1-dev, gnome-pilot (>= 0.1.62), libpisock-dev, libkrb5-dev
Standards-Version: 3.5.2.0

Package: evolution
Section: mail
Architecture: any
Depends: gtkhtml (>= 1.0.0), libcamel0 (= ${Source-Version}), ${shlibs:Depends}
Suggests: bugbuddy
Conflicts: evolution-ssl, evolution-dev
Replaces: evolution-ssl, evolution-dev
Provides: evolution-ssl, mail-reader, imap-client
Suggests: gnupg, gnome-spell
Description: The groupware suite
 Evolution is the integrated mail, calendar and address book 
 distributed suite from Ximian, Inc.
 .
 See http://www.ximian.com/products/ximian_evolution/index.html for more
 information.

Package: libcamel0
Section: libs
Architecture: any
Depends: ${shlibs:Depends}, libnss3, libnspr4
Conflicts: libcamel-ssl0
Replaces: libcamel-ssl0
Description: A generic Messaging Library
 Camel will be a generic messaging library. It will eventually
 support the standard messaging system for receiving and sending
 messages.
 It aims at being the backend for the future gnome-mailer system.
 .
 The name "camel" stands for ... nothing. Open area of development
 there.
 You know, that "bazaar" thing. Maybe could we organize a big
 contest on gnome-list to find the best explanation :)
 .
 Camel draws heavily from JavaMail and the IMAP4rev1 RFC. People
 wanting to hack on a provider should read the JavaMail API
 specification, but CMC and MAPI are of interest too.

Package: libcamel-dev
Section: devel
Architecture: any
Conflicts: libcamel-ssl-dev
Replaces: libcamel-ssl-dev
Depends: libcamel0 (= ${Source-Version})
Description: generic messaging library -- development files
 camel development static libraries and header files.