radicale2 is a far-reaching rewrite (requiring python3) with significant performance improvements: http://radicale.org/1to2/
Can you provide a patch?
Unfortunately I can't, because the changes from version 1 to 2 are extensive (as described in the link), and I'm not experienced in port maintenance.
Created attachment 191588 [details]
Update to 2.1.8.
* update to 2.1.8
* add TEST_DEPENDS
* remove OPTIONS
Not really tested, I do not use www/radicale, and I am not feeling setting it up just to test. :-D
* 'poudriere testport' went fine.
* the builtin python test: passed 20/22.
 I could not find any reference to them anywhere for this version.
Reassign to sunpoet who has taken maintainership in the meantime.
If we add Radicale 2 as www/radicale2 it would given users a chance
to migrate to it from Radicale 1.
Created attachment 191766 [details]
patch to add as www/radicale2
I attach a patch in case of www/radicale become www/radicale2.
Created attachment 191937 [details]
patch to add as www/radicale2
The previous patch had a change in www/Makefile what does not belong to this bug.
Created attachment 192355 [details]
Updated new port of www/radicale2
I've tested the submitted www/radicale2 (v2.1.8) on DragonFly BSD (which also uses a slightly patched Ports Collection from FreeBSD). Since I want to use uWSGI with Radicale, but the current version misses the .wsgi script shipped by the upstream.
I attached an updated version with the .wsgi and .fcgi scripts also being installed. Radicale2 currently runs fine on my DragonFly BSD machine.
As mentioned by Alexandre C. Guimarães that the builtin python tests failed on two of the tests, both of them are PEP8 styles problems, so should be fine.
P.S. I didn't checkout the FreeBSD Ports Collection via svn, so I just created a shell archive (.shar) for my updated version of www/radicale2.
Thanks guys, that port is quite good already. I only had to fix the path to the config in the rc startscript and add a shebangfix for the fcgi and wsgi scripts. Now it builds fine with poudriere, portlint is silent and it runs fine.
I'd say it's okay to commit it to the portstree. I also think it makes sense to add it as a new port because the upgrade from 1.x to 2.x requires people to export the data with 1.x or you won't be able to access your data with 2.x. It's described in https://radicale.org/1to2/
@Sunpoet Do you want to go ahead and commit it?
Created attachment 193481 [details]
Comment #9 I tried your shell archive and building the port work well.
I think it is necessary to add a message after the installation to:
- advising a migration of the data if it's an upgrade from 1.x.x to 2.x.x. Including this link https://radicale.org/1to2/
- advising to follow the documentation at https://radicale.org/documentation/ to configure the server
- advising to install apache24 if the htpasswd tool is needed to handle securly the htpasswd file
A commit references this bug:
Date: Tue Jun 12 14:19:18 UTC 2018
New revision: 472256
Radicale is a small but powerful CalDAV (calendars, todo-lists) and CardDAV
(contacts) server, that:
Shares calendars through CalDAV, WebDAV and HTTP.
Shares contacts through CardDAV, WebDAV and HTTP.
Supports events, todos, journal entries and business cards.
Works out-of-the-box, no installation nor configuration required.
Can warn users on concurrent editing.
Can limit access by authentication.
Can secure connections.
Works with many CalDAV and CardDAV clients.
Is GPLv3-licensed free software.
Submitted by: Alexandre C. Guimaraes <email@example.com>
Thanks to all people involved! Since sunpoet did not respond I have taken over maintainership for the port and committed it.
Beware when updating from radicale 1.x to follow the migration instructions (also mentiond in pkg-message).