horde/kolab_storage

Kolab data storage library

2.2.4 2019-11-03 00:00 UTC

Requires

• php: ^5.3 || ^7
• pear-pear.horde.org/horde_cache: ^2
• pear-pear.horde.org/horde_exception: ^2
• pear-pear.horde.org/horde_kolab_format: ^2
• pear-pear.horde.org/horde_mime: ^2
• pear-pear.horde.org/horde_support: ^2
• pear-pear.horde.org/horde_translation: ^2.2
• pear-pear.horde.org/horde_util: ^2

Suggests

• ext-imap: *
• pear-pear.horde.org/Horde_History: ^2
• pear-pear.horde.org/Horde_Imap_Client: ^2.14
• pear-pear.horde.org/Horde_Test: ^2.1
• pear-pear.php.net/HTTP_Request: *
• pear-pear.php.net/Net_IMAP: ^1.1

Replaces

• pear-horde/horde_kolab_storage: 2.*
• pear-pear.horde.org/horde_kolab_storage: 2.*

LGPL-2.1

• Michael J Rubinsky
• Gunnar Wrobel

README

Requests against upstream

• use maintaina-bare branch for pure code changes without touching composer.json, package.xml, changelog and with minimal edits to .horde.yml if required

Requests against this repo

• use maintaina-bare branch for pure code changes. Do not touch metadata files.

Upgrading this repo

• rebase horde-upstream branch on horde upstream repo
• rebase maintaina-bare on horde-upstream and fix any conflicts
• rebase maintaina-composerfixed on maintaina-bare or drop and recreate the branch. Then generate a new composer.json. You will probably need a custom components/config/bin for a satis repo or downstream git repo
• rebase master branch on maintaina-composerfixed. This should never fail as they only differ by this readme