2021-03-11 15:35:52 +01:00
|
|
|
# $NetBSD: Makefile,v 1.3 2021/03/11 14:35:52 triaxx Exp $
|
2020-02-11 21:36:49 +01:00
|
|
|
|
roundcube-plugin-carddav: Update to 4.0.4
pkgsrc changes:
---------------
* The main maintainer seems to have changed. The GitHub repository has been
updated accordingly.
* Since the vendor dependencies has been removed from the Github release, we
use php-composer to resolve them.
upstream changes:
-----------------
Version 4.0.4 (to 4.0.3)
o Fix #321: Boolean settings in presets caused errors when trying to store
the preset's addressbooks to the database
o Fix #322: The refresh time string from admin presets was not converted to
seconds, causing errors or wrong values when storing the preset's
addressbooks to the database
o Fix #324: Changes not immediately visible with postgresql (delete contact,
add/remove contact to/from group)
o Fix: spurious error returned when creating VCard on Google
Version 4.0.3 (to 4.0.2)
o Allow release 1.0 of carddavclient in composer dependencies
o No changes to the plugin itself
Version 4.0.2 (to 4.0.1)
o Fix #316: Incompatibility with Sabre/VObject version 4 preventing saving
contacts using custom labels
o Fix: Default refresh time set to 1 sec in settings
Version 4.0.1 (to 4.0.0)
o Fix: Plugin version was not shown in about window for tarball installations
o Fix: Collation behavior was case-insensitive for MySQL (only). Now unified
across the different supported DBMS.
o Fix #306: With MySQL, sync failure could occur when several custom labels
where used that only differed in case (effect of previous issue).
o Fix #308: With SQLite, the initial sync after adding a new addressbook was
not automatically triggered.
Version 4.0.0 (to 3.0.3)
This release contains changes to DB schema. The database will be migrated
automatically upon login to roundcube.
o All changes from 4.0.0-alpha1
o Fix: Deletion of empty CATEGORIES-type groups
o Fix: Delete CATEGORIES-type groups from DB that become empty during a sync
o Fix: Renaming of empty CATEGORIES-type groups
o Fix: During deletion, do not rely on the DB's ON CASCADE DELETE because
this is disabled by default for SQLite
o Fix: It was not possible to discover multiple addressbooks for an admin
preset because of a wrong UNIQUE constraint in MySQL
o Fix: Catch exceptions thrown inside the plugin (avoid "white page" on error)
o Increase the maximum lengths of password, email and url fields
o Use transactions to synchronize concurrent operations on the same
addressbook (data consistency issues may still occur with MySQL because of
roundcube DB layer bug). For details, see DBSYNC.md.
o Unified database indexes across the different database backends: Create
indexes for foreign key columns (PostgreSQL, SQLite)
o Fixed issues in the migration scripts and added SQL scripts showing the
current DB schema
o Update hungarian translation (thanks to @tsabi)
Version 4.0.0-alpha1 (to 3.0.3)
Note: The Changelog for this version is not complete
This is an alpha release because I did not perform any tests on it.
Nevertheless, it has many bugs fixed and I encourage you to upgrade and report
issues as you find them. The last release 3.0.3 has many issues that have been
fixed with in v4. I push this release early mainly because of the security
issue reported. I'll continue working on remaining issues I want to fix (note:
all of them are also present in 3.0.3) for v4 and I intend release a more
tested version and a more detailed changelog within the next weeks.
o Security issue: It was possible to read data from other user's
addressbooks. Depending on the configuration, it might also have been
possible to change data in their addressbooks. Thanks to @cnmicha for
reporting this issue. This issue affects all previously released versions
of RCMCardDAV using a database cache.
o Many bugs you reported and several more I discovered during refactoring
have been fixed.
o The password scheme now defaults to encrypted (if you have not configured a
password scheme, this will take effect automatically for newly stored
password. If you don't want this, configure a password scheme in
settings.php).
o The URL is not changeable after creation of an addressbook anymore. It used
to work in specific, but not all cases. As the behavior is potentially
broken and not easy to fix, it is removed for now.
o The two kinds of contact groups (VCard-based vs. CATEGORIES-based) are not
transparently supported to the possible extent. The configuration switch is
only meaningful concerning the type of group used when a new group is
created from RCMCardDAV. See details here.
o The CardDAV interaction is moved to a library. It is essentially a complete
rewrite of the code communicating with the CardDAV servers and includes
interoperability tests with many common servers, see here.
2021-02-26 14:17:36 +01:00
|
|
|
DISTNAME= carddav-v4.0.4
|
2021-03-11 15:35:52 +01:00
|
|
|
PKGREVISION= 1
|
roundcube-plugin-carddav: Update to 4.0.4
pkgsrc changes:
---------------
* The main maintainer seems to have changed. The GitHub repository has been
updated accordingly.
* Since the vendor dependencies has been removed from the Github release, we
use php-composer to resolve them.
upstream changes:
-----------------
Version 4.0.4 (to 4.0.3)
o Fix #321: Boolean settings in presets caused errors when trying to store
the preset's addressbooks to the database
o Fix #322: The refresh time string from admin presets was not converted to
seconds, causing errors or wrong values when storing the preset's
addressbooks to the database
o Fix #324: Changes not immediately visible with postgresql (delete contact,
add/remove contact to/from group)
o Fix: spurious error returned when creating VCard on Google
Version 4.0.3 (to 4.0.2)
o Allow release 1.0 of carddavclient in composer dependencies
o No changes to the plugin itself
Version 4.0.2 (to 4.0.1)
o Fix #316: Incompatibility with Sabre/VObject version 4 preventing saving
contacts using custom labels
o Fix: Default refresh time set to 1 sec in settings
Version 4.0.1 (to 4.0.0)
o Fix: Plugin version was not shown in about window for tarball installations
o Fix: Collation behavior was case-insensitive for MySQL (only). Now unified
across the different supported DBMS.
o Fix #306: With MySQL, sync failure could occur when several custom labels
where used that only differed in case (effect of previous issue).
o Fix #308: With SQLite, the initial sync after adding a new addressbook was
not automatically triggered.
Version 4.0.0 (to 3.0.3)
This release contains changes to DB schema. The database will be migrated
automatically upon login to roundcube.
o All changes from 4.0.0-alpha1
o Fix: Deletion of empty CATEGORIES-type groups
o Fix: Delete CATEGORIES-type groups from DB that become empty during a sync
o Fix: Renaming of empty CATEGORIES-type groups
o Fix: During deletion, do not rely on the DB's ON CASCADE DELETE because
this is disabled by default for SQLite
o Fix: It was not possible to discover multiple addressbooks for an admin
preset because of a wrong UNIQUE constraint in MySQL
o Fix: Catch exceptions thrown inside the plugin (avoid "white page" on error)
o Increase the maximum lengths of password, email and url fields
o Use transactions to synchronize concurrent operations on the same
addressbook (data consistency issues may still occur with MySQL because of
roundcube DB layer bug). For details, see DBSYNC.md.
o Unified database indexes across the different database backends: Create
indexes for foreign key columns (PostgreSQL, SQLite)
o Fixed issues in the migration scripts and added SQL scripts showing the
current DB schema
o Update hungarian translation (thanks to @tsabi)
Version 4.0.0-alpha1 (to 3.0.3)
Note: The Changelog for this version is not complete
This is an alpha release because I did not perform any tests on it.
Nevertheless, it has many bugs fixed and I encourage you to upgrade and report
issues as you find them. The last release 3.0.3 has many issues that have been
fixed with in v4. I push this release early mainly because of the security
issue reported. I'll continue working on remaining issues I want to fix (note:
all of them are also present in 3.0.3) for v4 and I intend release a more
tested version and a more detailed changelog within the next weeks.
o Security issue: It was possible to read data from other user's
addressbooks. Depending on the configuration, it might also have been
possible to change data in their addressbooks. Thanks to @cnmicha for
reporting this issue. This issue affects all previously released versions
of RCMCardDAV using a database cache.
o Many bugs you reported and several more I discovered during refactoring
have been fixed.
o The password scheme now defaults to encrypted (if you have not configured a
password scheme, this will take effect automatically for newly stored
password. If you don't want this, configure a password scheme in
settings.php).
o The URL is not changeable after creation of an addressbook anymore. It used
to work in specific, but not all cases. As the behavior is potentially
broken and not easy to fix, it is removed for now.
o The two kinds of contact groups (VCard-based vs. CATEGORIES-based) are not
transparently supported to the possible extent. The configuration switch is
only meaningful concerning the type of group used when a new group is
created from RCMCardDAV. See details here.
o The CardDAV interaction is moved to a library. It is essentially a complete
rewrite of the code communicating with the CardDAV servers and includes
interoperability tests with many common servers, see here.
2021-02-26 14:17:36 +01:00
|
|
|
PKGNAME= ${PHP_PKG_PREFIX}-roundcube-plugin-${DISTNAME:S/-v/-/}
|
2020-02-11 21:36:49 +01:00
|
|
|
CATEGORIES= mail
|
roundcube-plugin-carddav: Update to 4.0.4
pkgsrc changes:
---------------
* The main maintainer seems to have changed. The GitHub repository has been
updated accordingly.
* Since the vendor dependencies has been removed from the Github release, we
use php-composer to resolve them.
upstream changes:
-----------------
Version 4.0.4 (to 4.0.3)
o Fix #321: Boolean settings in presets caused errors when trying to store
the preset's addressbooks to the database
o Fix #322: The refresh time string from admin presets was not converted to
seconds, causing errors or wrong values when storing the preset's
addressbooks to the database
o Fix #324: Changes not immediately visible with postgresql (delete contact,
add/remove contact to/from group)
o Fix: spurious error returned when creating VCard on Google
Version 4.0.3 (to 4.0.2)
o Allow release 1.0 of carddavclient in composer dependencies
o No changes to the plugin itself
Version 4.0.2 (to 4.0.1)
o Fix #316: Incompatibility with Sabre/VObject version 4 preventing saving
contacts using custom labels
o Fix: Default refresh time set to 1 sec in settings
Version 4.0.1 (to 4.0.0)
o Fix: Plugin version was not shown in about window for tarball installations
o Fix: Collation behavior was case-insensitive for MySQL (only). Now unified
across the different supported DBMS.
o Fix #306: With MySQL, sync failure could occur when several custom labels
where used that only differed in case (effect of previous issue).
o Fix #308: With SQLite, the initial sync after adding a new addressbook was
not automatically triggered.
Version 4.0.0 (to 3.0.3)
This release contains changes to DB schema. The database will be migrated
automatically upon login to roundcube.
o All changes from 4.0.0-alpha1
o Fix: Deletion of empty CATEGORIES-type groups
o Fix: Delete CATEGORIES-type groups from DB that become empty during a sync
o Fix: Renaming of empty CATEGORIES-type groups
o Fix: During deletion, do not rely on the DB's ON CASCADE DELETE because
this is disabled by default for SQLite
o Fix: It was not possible to discover multiple addressbooks for an admin
preset because of a wrong UNIQUE constraint in MySQL
o Fix: Catch exceptions thrown inside the plugin (avoid "white page" on error)
o Increase the maximum lengths of password, email and url fields
o Use transactions to synchronize concurrent operations on the same
addressbook (data consistency issues may still occur with MySQL because of
roundcube DB layer bug). For details, see DBSYNC.md.
o Unified database indexes across the different database backends: Create
indexes for foreign key columns (PostgreSQL, SQLite)
o Fixed issues in the migration scripts and added SQL scripts showing the
current DB schema
o Update hungarian translation (thanks to @tsabi)
Version 4.0.0-alpha1 (to 3.0.3)
Note: The Changelog for this version is not complete
This is an alpha release because I did not perform any tests on it.
Nevertheless, it has many bugs fixed and I encourage you to upgrade and report
issues as you find them. The last release 3.0.3 has many issues that have been
fixed with in v4. I push this release early mainly because of the security
issue reported. I'll continue working on remaining issues I want to fix (note:
all of them are also present in 3.0.3) for v4 and I intend release a more
tested version and a more detailed changelog within the next weeks.
o Security issue: It was possible to read data from other user's
addressbooks. Depending on the configuration, it might also have been
possible to change data in their addressbooks. Thanks to @cnmicha for
reporting this issue. This issue affects all previously released versions
of RCMCardDAV using a database cache.
o Many bugs you reported and several more I discovered during refactoring
have been fixed.
o The password scheme now defaults to encrypted (if you have not configured a
password scheme, this will take effect automatically for newly stored
password. If you don't want this, configure a password scheme in
settings.php).
o The URL is not changeable after creation of an addressbook anymore. It used
to work in specific, but not all cases. As the behavior is potentially
broken and not easy to fix, it is removed for now.
o The two kinds of contact groups (VCard-based vs. CATEGORIES-based) are not
transparently supported to the possible extent. The configuration switch is
only meaningful concerning the type of group used when a new group is
created from RCMCardDAV. See details here.
o The CardDAV interaction is moved to a library. It is essentially a complete
rewrite of the code communicating with the CardDAV servers and includes
interoperability tests with many common servers, see here.
2021-02-26 14:17:36 +01:00
|
|
|
MASTER_SITES= ${MASTER_SITE_GITHUB:=mstilkerich/}
|
2020-02-11 21:36:49 +01:00
|
|
|
GITHUB_PROJECT= rcmcarddav
|
|
|
|
|
GITHUB_RELEASE= v${PKGVERSION_NOREV}
|
roundcube-plugin-carddav: Update to 4.0.4
pkgsrc changes:
---------------
* The main maintainer seems to have changed. The GitHub repository has been
updated accordingly.
* Since the vendor dependencies has been removed from the Github release, we
use php-composer to resolve them.
upstream changes:
-----------------
Version 4.0.4 (to 4.0.3)
o Fix #321: Boolean settings in presets caused errors when trying to store
the preset's addressbooks to the database
o Fix #322: The refresh time string from admin presets was not converted to
seconds, causing errors or wrong values when storing the preset's
addressbooks to the database
o Fix #324: Changes not immediately visible with postgresql (delete contact,
add/remove contact to/from group)
o Fix: spurious error returned when creating VCard on Google
Version 4.0.3 (to 4.0.2)
o Allow release 1.0 of carddavclient in composer dependencies
o No changes to the plugin itself
Version 4.0.2 (to 4.0.1)
o Fix #316: Incompatibility with Sabre/VObject version 4 preventing saving
contacts using custom labels
o Fix: Default refresh time set to 1 sec in settings
Version 4.0.1 (to 4.0.0)
o Fix: Plugin version was not shown in about window for tarball installations
o Fix: Collation behavior was case-insensitive for MySQL (only). Now unified
across the different supported DBMS.
o Fix #306: With MySQL, sync failure could occur when several custom labels
where used that only differed in case (effect of previous issue).
o Fix #308: With SQLite, the initial sync after adding a new addressbook was
not automatically triggered.
Version 4.0.0 (to 3.0.3)
This release contains changes to DB schema. The database will be migrated
automatically upon login to roundcube.
o All changes from 4.0.0-alpha1
o Fix: Deletion of empty CATEGORIES-type groups
o Fix: Delete CATEGORIES-type groups from DB that become empty during a sync
o Fix: Renaming of empty CATEGORIES-type groups
o Fix: During deletion, do not rely on the DB's ON CASCADE DELETE because
this is disabled by default for SQLite
o Fix: It was not possible to discover multiple addressbooks for an admin
preset because of a wrong UNIQUE constraint in MySQL
o Fix: Catch exceptions thrown inside the plugin (avoid "white page" on error)
o Increase the maximum lengths of password, email and url fields
o Use transactions to synchronize concurrent operations on the same
addressbook (data consistency issues may still occur with MySQL because of
roundcube DB layer bug). For details, see DBSYNC.md.
o Unified database indexes across the different database backends: Create
indexes for foreign key columns (PostgreSQL, SQLite)
o Fixed issues in the migration scripts and added SQL scripts showing the
current DB schema
o Update hungarian translation (thanks to @tsabi)
Version 4.0.0-alpha1 (to 3.0.3)
Note: The Changelog for this version is not complete
This is an alpha release because I did not perform any tests on it.
Nevertheless, it has many bugs fixed and I encourage you to upgrade and report
issues as you find them. The last release 3.0.3 has many issues that have been
fixed with in v4. I push this release early mainly because of the security
issue reported. I'll continue working on remaining issues I want to fix (note:
all of them are also present in 3.0.3) for v4 and I intend release a more
tested version and a more detailed changelog within the next weeks.
o Security issue: It was possible to read data from other user's
addressbooks. Depending on the configuration, it might also have been
possible to change data in their addressbooks. Thanks to @cnmicha for
reporting this issue. This issue affects all previously released versions
of RCMCardDAV using a database cache.
o Many bugs you reported and several more I discovered during refactoring
have been fixed.
o The password scheme now defaults to encrypted (if you have not configured a
password scheme, this will take effect automatically for newly stored
password. If you don't want this, configure a password scheme in
settings.php).
o The URL is not changeable after creation of an addressbook anymore. It used
to work in specific, but not all cases. As the behavior is potentially
broken and not easy to fix, it is removed for now.
o The two kinds of contact groups (VCard-based vs. CATEGORIES-based) are not
transparently supported to the possible extent. The configuration switch is
only meaningful concerning the type of group used when a new group is
created from RCMCardDAV. See details here.
o The CardDAV interaction is moved to a library. It is essentially a complete
rewrite of the code communicating with the CardDAV servers and includes
interoperability tests with many common servers, see here.
2021-02-26 14:17:36 +01:00
|
|
|
EXTRACT_SUFX= .tgz
|
2020-02-11 21:36:49 +01:00
|
|
|
|
|
|
|
|
HOMEPAGE= https://www.benjamin-schieder.de/carddav.html
|
|
|
|
|
MAINTAINER= triaxx@NetBSD.org
|
|
|
|
|
COMMENT= CardDAV adapter for Roundcube
|
|
|
|
|
LICENSE= gnu-gpl-v2
|
|
|
|
|
|
|
|
|
|
.include "../../mk/bsd.prefs.mk"
|
|
|
|
|
|
roundcube-plugin-carddav: Update to 4.0.4
pkgsrc changes:
---------------
* The main maintainer seems to have changed. The GitHub repository has been
updated accordingly.
* Since the vendor dependencies has been removed from the Github release, we
use php-composer to resolve them.
upstream changes:
-----------------
Version 4.0.4 (to 4.0.3)
o Fix #321: Boolean settings in presets caused errors when trying to store
the preset's addressbooks to the database
o Fix #322: The refresh time string from admin presets was not converted to
seconds, causing errors or wrong values when storing the preset's
addressbooks to the database
o Fix #324: Changes not immediately visible with postgresql (delete contact,
add/remove contact to/from group)
o Fix: spurious error returned when creating VCard on Google
Version 4.0.3 (to 4.0.2)
o Allow release 1.0 of carddavclient in composer dependencies
o No changes to the plugin itself
Version 4.0.2 (to 4.0.1)
o Fix #316: Incompatibility with Sabre/VObject version 4 preventing saving
contacts using custom labels
o Fix: Default refresh time set to 1 sec in settings
Version 4.0.1 (to 4.0.0)
o Fix: Plugin version was not shown in about window for tarball installations
o Fix: Collation behavior was case-insensitive for MySQL (only). Now unified
across the different supported DBMS.
o Fix #306: With MySQL, sync failure could occur when several custom labels
where used that only differed in case (effect of previous issue).
o Fix #308: With SQLite, the initial sync after adding a new addressbook was
not automatically triggered.
Version 4.0.0 (to 3.0.3)
This release contains changes to DB schema. The database will be migrated
automatically upon login to roundcube.
o All changes from 4.0.0-alpha1
o Fix: Deletion of empty CATEGORIES-type groups
o Fix: Delete CATEGORIES-type groups from DB that become empty during a sync
o Fix: Renaming of empty CATEGORIES-type groups
o Fix: During deletion, do not rely on the DB's ON CASCADE DELETE because
this is disabled by default for SQLite
o Fix: It was not possible to discover multiple addressbooks for an admin
preset because of a wrong UNIQUE constraint in MySQL
o Fix: Catch exceptions thrown inside the plugin (avoid "white page" on error)
o Increase the maximum lengths of password, email and url fields
o Use transactions to synchronize concurrent operations on the same
addressbook (data consistency issues may still occur with MySQL because of
roundcube DB layer bug). For details, see DBSYNC.md.
o Unified database indexes across the different database backends: Create
indexes for foreign key columns (PostgreSQL, SQLite)
o Fixed issues in the migration scripts and added SQL scripts showing the
current DB schema
o Update hungarian translation (thanks to @tsabi)
Version 4.0.0-alpha1 (to 3.0.3)
Note: The Changelog for this version is not complete
This is an alpha release because I did not perform any tests on it.
Nevertheless, it has many bugs fixed and I encourage you to upgrade and report
issues as you find them. The last release 3.0.3 has many issues that have been
fixed with in v4. I push this release early mainly because of the security
issue reported. I'll continue working on remaining issues I want to fix (note:
all of them are also present in 3.0.3) for v4 and I intend release a more
tested version and a more detailed changelog within the next weeks.
o Security issue: It was possible to read data from other user's
addressbooks. Depending on the configuration, it might also have been
possible to change data in their addressbooks. Thanks to @cnmicha for
reporting this issue. This issue affects all previously released versions
of RCMCardDAV using a database cache.
o Many bugs you reported and several more I discovered during refactoring
have been fixed.
o The password scheme now defaults to encrypted (if you have not configured a
password scheme, this will take effect automatically for newly stored
password. If you don't want this, configure a password scheme in
settings.php).
o The URL is not changeable after creation of an addressbook anymore. It used
to work in specific, but not all cases. As the behavior is potentially
broken and not easy to fix, it is removed for now.
o The two kinds of contact groups (VCard-based vs. CATEGORIES-based) are not
transparently supported to the possible extent. The configuration switch is
only meaningful concerning the type of group used when a new group is
created from RCMCardDAV. See details here.
o The CardDAV interaction is moved to a library. It is essentially a complete
rewrite of the code communicating with the CardDAV servers and includes
interoperability tests with many common servers, see here.
2021-02-26 14:17:36 +01:00
|
|
|
NO_CONFIGURE= yes
|
2020-02-11 21:36:49 +01:00
|
|
|
NO_BUILD= yes
|
|
|
|
|
|
roundcube-plugin-carddav: Update to 4.0.4
pkgsrc changes:
---------------
* The main maintainer seems to have changed. The GitHub repository has been
updated accordingly.
* Since the vendor dependencies has been removed from the Github release, we
use php-composer to resolve them.
upstream changes:
-----------------
Version 4.0.4 (to 4.0.3)
o Fix #321: Boolean settings in presets caused errors when trying to store
the preset's addressbooks to the database
o Fix #322: The refresh time string from admin presets was not converted to
seconds, causing errors or wrong values when storing the preset's
addressbooks to the database
o Fix #324: Changes not immediately visible with postgresql (delete contact,
add/remove contact to/from group)
o Fix: spurious error returned when creating VCard on Google
Version 4.0.3 (to 4.0.2)
o Allow release 1.0 of carddavclient in composer dependencies
o No changes to the plugin itself
Version 4.0.2 (to 4.0.1)
o Fix #316: Incompatibility with Sabre/VObject version 4 preventing saving
contacts using custom labels
o Fix: Default refresh time set to 1 sec in settings
Version 4.0.1 (to 4.0.0)
o Fix: Plugin version was not shown in about window for tarball installations
o Fix: Collation behavior was case-insensitive for MySQL (only). Now unified
across the different supported DBMS.
o Fix #306: With MySQL, sync failure could occur when several custom labels
where used that only differed in case (effect of previous issue).
o Fix #308: With SQLite, the initial sync after adding a new addressbook was
not automatically triggered.
Version 4.0.0 (to 3.0.3)
This release contains changes to DB schema. The database will be migrated
automatically upon login to roundcube.
o All changes from 4.0.0-alpha1
o Fix: Deletion of empty CATEGORIES-type groups
o Fix: Delete CATEGORIES-type groups from DB that become empty during a sync
o Fix: Renaming of empty CATEGORIES-type groups
o Fix: During deletion, do not rely on the DB's ON CASCADE DELETE because
this is disabled by default for SQLite
o Fix: It was not possible to discover multiple addressbooks for an admin
preset because of a wrong UNIQUE constraint in MySQL
o Fix: Catch exceptions thrown inside the plugin (avoid "white page" on error)
o Increase the maximum lengths of password, email and url fields
o Use transactions to synchronize concurrent operations on the same
addressbook (data consistency issues may still occur with MySQL because of
roundcube DB layer bug). For details, see DBSYNC.md.
o Unified database indexes across the different database backends: Create
indexes for foreign key columns (PostgreSQL, SQLite)
o Fixed issues in the migration scripts and added SQL scripts showing the
current DB schema
o Update hungarian translation (thanks to @tsabi)
Version 4.0.0-alpha1 (to 3.0.3)
Note: The Changelog for this version is not complete
This is an alpha release because I did not perform any tests on it.
Nevertheless, it has many bugs fixed and I encourage you to upgrade and report
issues as you find them. The last release 3.0.3 has many issues that have been
fixed with in v4. I push this release early mainly because of the security
issue reported. I'll continue working on remaining issues I want to fix (note:
all of them are also present in 3.0.3) for v4 and I intend release a more
tested version and a more detailed changelog within the next weeks.
o Security issue: It was possible to read data from other user's
addressbooks. Depending on the configuration, it might also have been
possible to change data in their addressbooks. Thanks to @cnmicha for
reporting this issue. This issue affects all previously released versions
of RCMCardDAV using a database cache.
o Many bugs you reported and several more I discovered during refactoring
have been fixed.
o The password scheme now defaults to encrypted (if you have not configured a
password scheme, this will take effect automatically for newly stored
password. If you don't want this, configure a password scheme in
settings.php).
o The URL is not changeable after creation of an addressbook anymore. It used
to work in specific, but not all cases. As the behavior is potentially
broken and not easy to fix, it is removed for now.
o The two kinds of contact groups (VCard-based vs. CATEGORIES-based) are not
transparently supported to the possible extent. The configuration switch is
only meaningful concerning the type of group used when a new group is
created from RCMCardDAV. See details here.
o The CardDAV interaction is moved to a library. It is essentially a complete
rewrite of the code communicating with the CardDAV servers and includes
interoperability tests with many common servers, see here.
2021-02-26 14:17:36 +01:00
|
|
|
REPLACE_PHP= vendor/roundcube/plugin-installer/src/bin/rcubeinitdb.sh
|
|
|
|
|
|
|
|
|
|
BUILD_DEPENDS+= ${PHP_PKG_PREFIX}-composer-[0-9]*:../../devel/php-composer
|
2020-02-11 21:36:49 +01:00
|
|
|
DEPENDS+= ${PHP_PKG_PREFIX}-roundcube>=1.0.0:../../mail/roundcube
|
|
|
|
|
|
|
|
|
|
WRKSRC= ${WRKDIR}/carddav
|
|
|
|
|
|
roundcube-plugin-carddav: Update to 4.0.4
pkgsrc changes:
---------------
* The main maintainer seems to have changed. The GitHub repository has been
updated accordingly.
* Since the vendor dependencies has been removed from the Github release, we
use php-composer to resolve them.
upstream changes:
-----------------
Version 4.0.4 (to 4.0.3)
o Fix #321: Boolean settings in presets caused errors when trying to store
the preset's addressbooks to the database
o Fix #322: The refresh time string from admin presets was not converted to
seconds, causing errors or wrong values when storing the preset's
addressbooks to the database
o Fix #324: Changes not immediately visible with postgresql (delete contact,
add/remove contact to/from group)
o Fix: spurious error returned when creating VCard on Google
Version 4.0.3 (to 4.0.2)
o Allow release 1.0 of carddavclient in composer dependencies
o No changes to the plugin itself
Version 4.0.2 (to 4.0.1)
o Fix #316: Incompatibility with Sabre/VObject version 4 preventing saving
contacts using custom labels
o Fix: Default refresh time set to 1 sec in settings
Version 4.0.1 (to 4.0.0)
o Fix: Plugin version was not shown in about window for tarball installations
o Fix: Collation behavior was case-insensitive for MySQL (only). Now unified
across the different supported DBMS.
o Fix #306: With MySQL, sync failure could occur when several custom labels
where used that only differed in case (effect of previous issue).
o Fix #308: With SQLite, the initial sync after adding a new addressbook was
not automatically triggered.
Version 4.0.0 (to 3.0.3)
This release contains changes to DB schema. The database will be migrated
automatically upon login to roundcube.
o All changes from 4.0.0-alpha1
o Fix: Deletion of empty CATEGORIES-type groups
o Fix: Delete CATEGORIES-type groups from DB that become empty during a sync
o Fix: Renaming of empty CATEGORIES-type groups
o Fix: During deletion, do not rely on the DB's ON CASCADE DELETE because
this is disabled by default for SQLite
o Fix: It was not possible to discover multiple addressbooks for an admin
preset because of a wrong UNIQUE constraint in MySQL
o Fix: Catch exceptions thrown inside the plugin (avoid "white page" on error)
o Increase the maximum lengths of password, email and url fields
o Use transactions to synchronize concurrent operations on the same
addressbook (data consistency issues may still occur with MySQL because of
roundcube DB layer bug). For details, see DBSYNC.md.
o Unified database indexes across the different database backends: Create
indexes for foreign key columns (PostgreSQL, SQLite)
o Fixed issues in the migration scripts and added SQL scripts showing the
current DB schema
o Update hungarian translation (thanks to @tsabi)
Version 4.0.0-alpha1 (to 3.0.3)
Note: The Changelog for this version is not complete
This is an alpha release because I did not perform any tests on it.
Nevertheless, it has many bugs fixed and I encourage you to upgrade and report
issues as you find them. The last release 3.0.3 has many issues that have been
fixed with in v4. I push this release early mainly because of the security
issue reported. I'll continue working on remaining issues I want to fix (note:
all of them are also present in 3.0.3) for v4 and I intend release a more
tested version and a more detailed changelog within the next weeks.
o Security issue: It was possible to read data from other user's
addressbooks. Depending on the configuration, it might also have been
possible to change data in their addressbooks. Thanks to @cnmicha for
reporting this issue. This issue affects all previously released versions
of RCMCardDAV using a database cache.
o Many bugs you reported and several more I discovered during refactoring
have been fixed.
o The password scheme now defaults to encrypted (if you have not configured a
password scheme, this will take effect automatically for newly stored
password. If you don't want this, configure a password scheme in
settings.php).
o The URL is not changeable after creation of an addressbook anymore. It used
to work in specific, but not all cases. As the behavior is potentially
broken and not easy to fix, it is removed for now.
o The two kinds of contact groups (VCard-based vs. CATEGORIES-based) are not
transparently supported to the possible extent. The configuration switch is
only meaningful concerning the type of group used when a new group is
created from RCMCardDAV. See details here.
o The CardDAV interaction is moved to a library. It is essentially a complete
rewrite of the code communicating with the CardDAV servers and includes
interoperability tests with many common servers, see here.
2021-02-26 14:17:36 +01:00
|
|
|
PHP_VERSIONS_ACCEPTED= 74 73
|
2020-02-11 21:36:49 +01:00
|
|
|
|
|
|
|
|
PKG_SYSCONFSUBDIR= roundcube
|
|
|
|
|
|
|
|
|
|
WWW_USER?= ${APACHE_USER}
|
|
|
|
|
WWW_GROUP?= ${APACHE_GROUP}
|
|
|
|
|
PKG_GROUPS_VARS+= WWW_GROUP
|
|
|
|
|
PKG_USERS_VARS= WWW_USER
|
|
|
|
|
BUILD_DEFS+= WWW_USER WWW_GROUP APACHE_USER APACHE_GROUP
|
|
|
|
|
|
|
|
|
|
RCDIR= share/roundcube
|
|
|
|
|
CDDIR= ${RCDIR}/plugins/carddav
|
|
|
|
|
EGDIR= share/examples/roundcube/plugins/carddav
|
|
|
|
|
|
roundcube-plugin-carddav: Update to 4.0.4
pkgsrc changes:
---------------
* The main maintainer seems to have changed. The GitHub repository has been
updated accordingly.
* Since the vendor dependencies has been removed from the Github release, we
use php-composer to resolve them.
upstream changes:
-----------------
Version 4.0.4 (to 4.0.3)
o Fix #321: Boolean settings in presets caused errors when trying to store
the preset's addressbooks to the database
o Fix #322: The refresh time string from admin presets was not converted to
seconds, causing errors or wrong values when storing the preset's
addressbooks to the database
o Fix #324: Changes not immediately visible with postgresql (delete contact,
add/remove contact to/from group)
o Fix: spurious error returned when creating VCard on Google
Version 4.0.3 (to 4.0.2)
o Allow release 1.0 of carddavclient in composer dependencies
o No changes to the plugin itself
Version 4.0.2 (to 4.0.1)
o Fix #316: Incompatibility with Sabre/VObject version 4 preventing saving
contacts using custom labels
o Fix: Default refresh time set to 1 sec in settings
Version 4.0.1 (to 4.0.0)
o Fix: Plugin version was not shown in about window for tarball installations
o Fix: Collation behavior was case-insensitive for MySQL (only). Now unified
across the different supported DBMS.
o Fix #306: With MySQL, sync failure could occur when several custom labels
where used that only differed in case (effect of previous issue).
o Fix #308: With SQLite, the initial sync after adding a new addressbook was
not automatically triggered.
Version 4.0.0 (to 3.0.3)
This release contains changes to DB schema. The database will be migrated
automatically upon login to roundcube.
o All changes from 4.0.0-alpha1
o Fix: Deletion of empty CATEGORIES-type groups
o Fix: Delete CATEGORIES-type groups from DB that become empty during a sync
o Fix: Renaming of empty CATEGORIES-type groups
o Fix: During deletion, do not rely on the DB's ON CASCADE DELETE because
this is disabled by default for SQLite
o Fix: It was not possible to discover multiple addressbooks for an admin
preset because of a wrong UNIQUE constraint in MySQL
o Fix: Catch exceptions thrown inside the plugin (avoid "white page" on error)
o Increase the maximum lengths of password, email and url fields
o Use transactions to synchronize concurrent operations on the same
addressbook (data consistency issues may still occur with MySQL because of
roundcube DB layer bug). For details, see DBSYNC.md.
o Unified database indexes across the different database backends: Create
indexes for foreign key columns (PostgreSQL, SQLite)
o Fixed issues in the migration scripts and added SQL scripts showing the
current DB schema
o Update hungarian translation (thanks to @tsabi)
Version 4.0.0-alpha1 (to 3.0.3)
Note: The Changelog for this version is not complete
This is an alpha release because I did not perform any tests on it.
Nevertheless, it has many bugs fixed and I encourage you to upgrade and report
issues as you find them. The last release 3.0.3 has many issues that have been
fixed with in v4. I push this release early mainly because of the security
issue reported. I'll continue working on remaining issues I want to fix (note:
all of them are also present in 3.0.3) for v4 and I intend release a more
tested version and a more detailed changelog within the next weeks.
o Security issue: It was possible to read data from other user's
addressbooks. Depending on the configuration, it might also have been
possible to change data in their addressbooks. Thanks to @cnmicha for
reporting this issue. This issue affects all previously released versions
of RCMCardDAV using a database cache.
o Many bugs you reported and several more I discovered during refactoring
have been fixed.
o The password scheme now defaults to encrypted (if you have not configured a
password scheme, this will take effect automatically for newly stored
password. If you don't want this, configure a password scheme in
settings.php).
o The URL is not changeable after creation of an addressbook anymore. It used
to work in specific, but not all cases. As the behavior is potentially
broken and not easy to fix, it is removed for now.
o The two kinds of contact groups (VCard-based vs. CATEGORIES-based) are not
transparently supported to the possible extent. The configuration switch is
only meaningful concerning the type of group used when a new group is
created from RCMCardDAV. See details here.
o The CardDAV interaction is moved to a library. It is essentially a complete
rewrite of the code communicating with the CardDAV servers and includes
interoperability tests with many common servers, see here.
2021-02-26 14:17:36 +01:00
|
|
|
CD_SUBDIRS= dbmigrations localization skins src vendor
|
2020-02-11 21:36:49 +01:00
|
|
|
|
|
|
|
|
.for d in ${CD_SUBDIRS}
|
|
|
|
|
INSTALLATION_DIRS+= ${CDDIR}/${d}
|
|
|
|
|
.endfor
|
|
|
|
|
INSTALLATION_DIRS+= ${EGDIR}
|
|
|
|
|
|
|
|
|
|
CONF_FILES_PERMS+= ${PREFIX}/${EGDIR}/config.inc.php \
|
|
|
|
|
${PKG_SYSCONFDIR}/plugins/carddav/config.inc.php \
|
|
|
|
|
${WWW_USER} ${WWW_GROUP} 0640
|
|
|
|
|
|
|
|
|
|
MESSAGE_SUBST+= PKG_SYSCONFDIR=${PKG_SYSCONFDIR}
|
|
|
|
|
SUBST_CLASSES+= cfg
|
|
|
|
|
SUBST_STAGE.cfg= pre-install
|
|
|
|
|
SUBST_MESSAGE.cfg= Fixing configuration files.
|
roundcube-plugin-carddav: Update to 4.0.4
pkgsrc changes:
---------------
* The main maintainer seems to have changed. The GitHub repository has been
updated accordingly.
* Since the vendor dependencies has been removed from the Github release, we
use php-composer to resolve them.
upstream changes:
-----------------
Version 4.0.4 (to 4.0.3)
o Fix #321: Boolean settings in presets caused errors when trying to store
the preset's addressbooks to the database
o Fix #322: The refresh time string from admin presets was not converted to
seconds, causing errors or wrong values when storing the preset's
addressbooks to the database
o Fix #324: Changes not immediately visible with postgresql (delete contact,
add/remove contact to/from group)
o Fix: spurious error returned when creating VCard on Google
Version 4.0.3 (to 4.0.2)
o Allow release 1.0 of carddavclient in composer dependencies
o No changes to the plugin itself
Version 4.0.2 (to 4.0.1)
o Fix #316: Incompatibility with Sabre/VObject version 4 preventing saving
contacts using custom labels
o Fix: Default refresh time set to 1 sec in settings
Version 4.0.1 (to 4.0.0)
o Fix: Plugin version was not shown in about window for tarball installations
o Fix: Collation behavior was case-insensitive for MySQL (only). Now unified
across the different supported DBMS.
o Fix #306: With MySQL, sync failure could occur when several custom labels
where used that only differed in case (effect of previous issue).
o Fix #308: With SQLite, the initial sync after adding a new addressbook was
not automatically triggered.
Version 4.0.0 (to 3.0.3)
This release contains changes to DB schema. The database will be migrated
automatically upon login to roundcube.
o All changes from 4.0.0-alpha1
o Fix: Deletion of empty CATEGORIES-type groups
o Fix: Delete CATEGORIES-type groups from DB that become empty during a sync
o Fix: Renaming of empty CATEGORIES-type groups
o Fix: During deletion, do not rely on the DB's ON CASCADE DELETE because
this is disabled by default for SQLite
o Fix: It was not possible to discover multiple addressbooks for an admin
preset because of a wrong UNIQUE constraint in MySQL
o Fix: Catch exceptions thrown inside the plugin (avoid "white page" on error)
o Increase the maximum lengths of password, email and url fields
o Use transactions to synchronize concurrent operations on the same
addressbook (data consistency issues may still occur with MySQL because of
roundcube DB layer bug). For details, see DBSYNC.md.
o Unified database indexes across the different database backends: Create
indexes for foreign key columns (PostgreSQL, SQLite)
o Fixed issues in the migration scripts and added SQL scripts showing the
current DB schema
o Update hungarian translation (thanks to @tsabi)
Version 4.0.0-alpha1 (to 3.0.3)
Note: The Changelog for this version is not complete
This is an alpha release because I did not perform any tests on it.
Nevertheless, it has many bugs fixed and I encourage you to upgrade and report
issues as you find them. The last release 3.0.3 has many issues that have been
fixed with in v4. I push this release early mainly because of the security
issue reported. I'll continue working on remaining issues I want to fix (note:
all of them are also present in 3.0.3) for v4 and I intend release a more
tested version and a more detailed changelog within the next weeks.
o Security issue: It was possible to read data from other user's
addressbooks. Depending on the configuration, it might also have been
possible to change data in their addressbooks. Thanks to @cnmicha for
reporting this issue. This issue affects all previously released versions
of RCMCardDAV using a database cache.
o Many bugs you reported and several more I discovered during refactoring
have been fixed.
o The password scheme now defaults to encrypted (if you have not configured a
password scheme, this will take effect automatically for newly stored
password. If you don't want this, configure a password scheme in
settings.php).
o The URL is not changeable after creation of an addressbook anymore. It used
to work in specific, but not all cases. As the behavior is potentially
broken and not easy to fix, it is removed for now.
o The two kinds of contact groups (VCard-based vs. CATEGORIES-based) are not
transparently supported to the possible extent. The configuration switch is
only meaningful concerning the type of group used when a new group is
created from RCMCardDAV. See details here.
o The CardDAV interaction is moved to a library. It is essentially a complete
rewrite of the code communicating with the CardDAV servers and includes
interoperability tests with many common servers, see here.
2021-02-26 14:17:36 +01:00
|
|
|
SUBST_FILES.cfg= carddav.php
|
2020-02-11 21:36:49 +01:00
|
|
|
SUBST_VARS.cfg= PKG_SYSCONFDIR
|
|
|
|
|
|
|
|
|
|
do-install:
|
roundcube-plugin-carddav: Update to 4.0.4
pkgsrc changes:
---------------
* The main maintainer seems to have changed. The GitHub repository has been
updated accordingly.
* Since the vendor dependencies has been removed from the Github release, we
use php-composer to resolve them.
upstream changes:
-----------------
Version 4.0.4 (to 4.0.3)
o Fix #321: Boolean settings in presets caused errors when trying to store
the preset's addressbooks to the database
o Fix #322: The refresh time string from admin presets was not converted to
seconds, causing errors or wrong values when storing the preset's
addressbooks to the database
o Fix #324: Changes not immediately visible with postgresql (delete contact,
add/remove contact to/from group)
o Fix: spurious error returned when creating VCard on Google
Version 4.0.3 (to 4.0.2)
o Allow release 1.0 of carddavclient in composer dependencies
o No changes to the plugin itself
Version 4.0.2 (to 4.0.1)
o Fix #316: Incompatibility with Sabre/VObject version 4 preventing saving
contacts using custom labels
o Fix: Default refresh time set to 1 sec in settings
Version 4.0.1 (to 4.0.0)
o Fix: Plugin version was not shown in about window for tarball installations
o Fix: Collation behavior was case-insensitive for MySQL (only). Now unified
across the different supported DBMS.
o Fix #306: With MySQL, sync failure could occur when several custom labels
where used that only differed in case (effect of previous issue).
o Fix #308: With SQLite, the initial sync after adding a new addressbook was
not automatically triggered.
Version 4.0.0 (to 3.0.3)
This release contains changes to DB schema. The database will be migrated
automatically upon login to roundcube.
o All changes from 4.0.0-alpha1
o Fix: Deletion of empty CATEGORIES-type groups
o Fix: Delete CATEGORIES-type groups from DB that become empty during a sync
o Fix: Renaming of empty CATEGORIES-type groups
o Fix: During deletion, do not rely on the DB's ON CASCADE DELETE because
this is disabled by default for SQLite
o Fix: It was not possible to discover multiple addressbooks for an admin
preset because of a wrong UNIQUE constraint in MySQL
o Fix: Catch exceptions thrown inside the plugin (avoid "white page" on error)
o Increase the maximum lengths of password, email and url fields
o Use transactions to synchronize concurrent operations on the same
addressbook (data consistency issues may still occur with MySQL because of
roundcube DB layer bug). For details, see DBSYNC.md.
o Unified database indexes across the different database backends: Create
indexes for foreign key columns (PostgreSQL, SQLite)
o Fixed issues in the migration scripts and added SQL scripts showing the
current DB schema
o Update hungarian translation (thanks to @tsabi)
Version 4.0.0-alpha1 (to 3.0.3)
Note: The Changelog for this version is not complete
This is an alpha release because I did not perform any tests on it.
Nevertheless, it has many bugs fixed and I encourage you to upgrade and report
issues as you find them. The last release 3.0.3 has many issues that have been
fixed with in v4. I push this release early mainly because of the security
issue reported. I'll continue working on remaining issues I want to fix (note:
all of them are also present in 3.0.3) for v4 and I intend release a more
tested version and a more detailed changelog within the next weeks.
o Security issue: It was possible to read data from other user's
addressbooks. Depending on the configuration, it might also have been
possible to change data in their addressbooks. Thanks to @cnmicha for
reporting this issue. This issue affects all previously released versions
of RCMCardDAV using a database cache.
o Many bugs you reported and several more I discovered during refactoring
have been fixed.
o The password scheme now defaults to encrypted (if you have not configured a
password scheme, this will take effect automatically for newly stored
password. If you don't want this, configure a password scheme in
settings.php).
o The URL is not changeable after creation of an addressbook anymore. It used
to work in specific, but not all cases. As the behavior is potentially
broken and not easy to fix, it is removed for now.
o The two kinds of contact groups (VCard-based vs. CATEGORIES-based) are not
transparently supported to the possible extent. The configuration switch is
only meaningful concerning the type of group used when a new group is
created from RCMCardDAV. See details here.
o The CardDAV interaction is moved to a library. It is essentially a complete
rewrite of the code communicating with the CardDAV servers and includes
interoperability tests with many common servers, see here.
2021-02-26 14:17:36 +01:00
|
|
|
cd ${WRKSRC} && ${PREFIX}/bin/composer install --no-dev
|
2020-02-11 21:36:49 +01:00
|
|
|
${INSTALL_DATA} ${WRKSRC}/carddav.php \
|
|
|
|
|
${DESTDIR}${PREFIX}/${CDDIR}/carddav.php
|
|
|
|
|
.for i in ${CD_SUBDIRS}
|
|
|
|
|
cd ${WRKSRC}/${i} && ${FIND} . -type f -print | \
|
|
|
|
|
pax -rw ${DESTDIR}${PREFIX}/${CDDIR}/${i}
|
|
|
|
|
${FIND} ${DESTDIR}${PREFIX}/${CDDIR}/${i} -type f | \
|
|
|
|
|
${XARGS} ${CHMOD} ${SHAREMODE}
|
|
|
|
|
${FIND} ${DESTDIR}${PREFIX}/${CDDIR}/${i} -type d | \
|
|
|
|
|
${XARGS} ${CHMOD} ${PKGDIRMODE}
|
|
|
|
|
${CHOWN} -R ${SHAREOWN}:${SHAREGRP} \
|
|
|
|
|
${DESTDIR}${PREFIX}/${CDDIR}/${i}
|
|
|
|
|
.endfor
|
|
|
|
|
${INSTALL_DATA} ${WRKSRC}/config.inc.php.dist \
|
|
|
|
|
${DESTDIR}${PREFIX}/${EGDIR}/config.inc.php
|
|
|
|
|
|
roundcube-plugin-carddav: Update to 4.0.4
pkgsrc changes:
---------------
* The main maintainer seems to have changed. The GitHub repository has been
updated accordingly.
* Since the vendor dependencies has been removed from the Github release, we
use php-composer to resolve them.
upstream changes:
-----------------
Version 4.0.4 (to 4.0.3)
o Fix #321: Boolean settings in presets caused errors when trying to store
the preset's addressbooks to the database
o Fix #322: The refresh time string from admin presets was not converted to
seconds, causing errors or wrong values when storing the preset's
addressbooks to the database
o Fix #324: Changes not immediately visible with postgresql (delete contact,
add/remove contact to/from group)
o Fix: spurious error returned when creating VCard on Google
Version 4.0.3 (to 4.0.2)
o Allow release 1.0 of carddavclient in composer dependencies
o No changes to the plugin itself
Version 4.0.2 (to 4.0.1)
o Fix #316: Incompatibility with Sabre/VObject version 4 preventing saving
contacts using custom labels
o Fix: Default refresh time set to 1 sec in settings
Version 4.0.1 (to 4.0.0)
o Fix: Plugin version was not shown in about window for tarball installations
o Fix: Collation behavior was case-insensitive for MySQL (only). Now unified
across the different supported DBMS.
o Fix #306: With MySQL, sync failure could occur when several custom labels
where used that only differed in case (effect of previous issue).
o Fix #308: With SQLite, the initial sync after adding a new addressbook was
not automatically triggered.
Version 4.0.0 (to 3.0.3)
This release contains changes to DB schema. The database will be migrated
automatically upon login to roundcube.
o All changes from 4.0.0-alpha1
o Fix: Deletion of empty CATEGORIES-type groups
o Fix: Delete CATEGORIES-type groups from DB that become empty during a sync
o Fix: Renaming of empty CATEGORIES-type groups
o Fix: During deletion, do not rely on the DB's ON CASCADE DELETE because
this is disabled by default for SQLite
o Fix: It was not possible to discover multiple addressbooks for an admin
preset because of a wrong UNIQUE constraint in MySQL
o Fix: Catch exceptions thrown inside the plugin (avoid "white page" on error)
o Increase the maximum lengths of password, email and url fields
o Use transactions to synchronize concurrent operations on the same
addressbook (data consistency issues may still occur with MySQL because of
roundcube DB layer bug). For details, see DBSYNC.md.
o Unified database indexes across the different database backends: Create
indexes for foreign key columns (PostgreSQL, SQLite)
o Fixed issues in the migration scripts and added SQL scripts showing the
current DB schema
o Update hungarian translation (thanks to @tsabi)
Version 4.0.0-alpha1 (to 3.0.3)
Note: The Changelog for this version is not complete
This is an alpha release because I did not perform any tests on it.
Nevertheless, it has many bugs fixed and I encourage you to upgrade and report
issues as you find them. The last release 3.0.3 has many issues that have been
fixed with in v4. I push this release early mainly because of the security
issue reported. I'll continue working on remaining issues I want to fix (note:
all of them are also present in 3.0.3) for v4 and I intend release a more
tested version and a more detailed changelog within the next weeks.
o Security issue: It was possible to read data from other user's
addressbooks. Depending on the configuration, it might also have been
possible to change data in their addressbooks. Thanks to @cnmicha for
reporting this issue. This issue affects all previously released versions
of RCMCardDAV using a database cache.
o Many bugs you reported and several more I discovered during refactoring
have been fixed.
o The password scheme now defaults to encrypted (if you have not configured a
password scheme, this will take effect automatically for newly stored
password. If you don't want this, configure a password scheme in
settings.php).
o The URL is not changeable after creation of an addressbook anymore. It used
to work in specific, but not all cases. As the behavior is potentially
broken and not easy to fix, it is removed for now.
o The two kinds of contact groups (VCard-based vs. CATEGORIES-based) are not
transparently supported to the possible extent. The configuration switch is
only meaningful concerning the type of group used when a new group is
created from RCMCardDAV. See details here.
o The CardDAV interaction is moved to a library. It is essentially a complete
rewrite of the code communicating with the CardDAV servers and includes
interoperability tests with many common servers, see here.
2021-02-26 14:17:36 +01:00
|
|
|
.include "../../lang/php/replace.mk"
|
2020-02-11 21:36:49 +01:00
|
|
|
.include "../../mk/bsd.pkg.mk"
|