Idea shamelessly stolen from 4e60b0efae.
I realized that I don't really know anymore where I'm listed as maintainer and what
I'm actually (co)-maintaining which means that I can't proactively take
care of packages I officially maintain.
As I don't have the time, energy and motivation to take care of stuff I
was interested in 1 or 2 years ago (or packaged for someone else in the
past), I decided that I make this explicit by removing myself from several
packages and adding myself in some other stuff I'm now interested in.
I've seen it several times now that people remove themselves from a
package without removing the package if it's unmaintained after that
which is why I figured that it's fine in my case as the affected pkgs
are rather low-prio and were pretty easy to maintain.
https://roundcube.net/news/2019/11/09/roundcube-1.4.0-released
* `curl` cmd in the test can fail as roundcube returns a http/401 if
unauthorized (and we're explicitly requesting the login form). By
checking if the `persistent_login` plugin is loaded, the assertion is
still valid)
* Use `$argv[0]` to determine install path in the installer script. I'm
not exactly sure why, but it seems as `__DIR__` now resolves symlinks
which breaks the installer if roundcube is in a `buildEnv` with
third-party plugins.
This function creates a new store path with roundcube sources and all
specified plugins. It can be used like this:
```
roundcube.withPlugins (plugins: with plugins; [
persistent_login
])
```
This is a service release to update the stable version 1.3 of Roundcube
Webmail. It contains fixes to several bugs backported from the master
branch including a security fix for a reported XSS vulnerability plus
updates to ensure compatibility with PHP 7.3 and recent versions of
Courier-IMAP, Dovecot and MySQL 8. See the complete changelog at
https://github.com/roundcube/roundcubemail/releases/tag/1.3.8
