as opposed to earlier threats, BerkDB was not entirely dropped; i suppose the isync 0.7 -> 0.8 change had a reason, so i added an alternative UID storage scheme. note that BDB 4.0 is not sufficient, as the db->open function changed in an incompatible way ... i updated the debian packaging except for a changelog entry. note that i removed the upgrade blurb, as upstream now has a smooth upgrade path down to at least isync 0.4.
		
			
				
	
	
		
			29 lines
		
	
	
	
		
			1.3 KiB
		
	
	
	
		
			Text
		
	
	
	
	
	
			
		
		
	
	
			29 lines
		
	
	
	
		
			1.3 KiB
		
	
	
	
		
			Text
		
	
	
	
	
	
Source: isync
 | 
						|
Section: mail
 | 
						|
Priority: optional
 | 
						|
Maintainer: Nicolas Boullis <nboullis@debian.org>
 | 
						|
Uploaders: Nicolas Boullis <nboullis@debian.org>, Theodore Y. Ts'o <tytso@mit.edu>
 | 
						|
Standards-Version: 3.6.1
 | 
						|
Build-Depends: libssl-dev, debhelper (>= 4.1.16), dpkg-dev (>= 1.9.0), libdb4.2-dev, dpatch
 | 
						|
 | 
						|
Package: isync
 | 
						|
Architecture: any
 | 
						|
Depends: ${shlibs:Depends}, ${misc:Depends}
 | 
						|
Suggests: mutt
 | 
						|
Description: Synchronize Maildir and IMAP4 mailboxes
 | 
						|
 A command line application which synchronizes mailboxes; currently
 | 
						|
 Maildir and IMAP4 mailboxes are supported.
 | 
						|
 New messages, message deletions and flag changes can be propagated both ways.
 | 
						|
 It is useful for working in disconnected mode, such as on a laptop or with a
 | 
						|
 non-permanent internet collection (dIMAP).
 | 
						|
 .
 | 
						|
 Features:
 | 
						|
  * Fine-grained selection of synchronization operations to perform
 | 
						|
  * Synchronizes single mailboxes or entire mailbox collections
 | 
						|
  * Partial mirrors possible: keep only the latest messages locally
 | 
						|
  * Trash functionality: backup messages before removing them
 | 
						|
  * IMAP features:
 | 
						|
    * Supports TLS/SSL via imaps: (port 993) and STARTTLS (RFC2595)
 | 
						|
    * Supports CRAM-MD5 (RFC2195) for authentication
 | 
						|
    * Supports NAMESPACE (RFC2342) for simplified configuration
 | 
						|
    * Pipelining for maximum speed (currently only partially implemented)
 |