Date: Thu, 27 Feb 2025 13:51:05 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 278045] [NEW PORT] deskutils/calendar_cli: Simple command-line CalDav client Message-ID: <bug-278045-7788-KjRnvge1pA@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-278045-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-278045-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D278045 --- Comment #4 from cos <freebsd.org@fydagy.netizen.se> --- TL;DR: Yes I think this software is still the relevant one to package, beca= use it is the version which actually works. That same section of the README also contains this sentence: > If you need a production-ready mature command-line utility for accessing = your calendar, then this is the right tool ... as for now. While the author has moved on to use plann instead, he has also publicly communicated the intent to continue maintaining calendar_cli, and accepts quality related PR:s (as stated in the same README). As always, the devil is in the details. In its current state plann is too b= uggy to be used for many use cases. I have attempted to migrate. Unlike calendar_cli, plann confuses different calendars. Depending (likely) on the server implementation, queries return all events for every calendar (includ= ing a completely different user's shared ones) regardless of filtering. CalDAV = is a complex protocol, for which libraries, clients and servers tend to take qui= te a while to mature. Ideally one should debug and fix the new tool, but for now calendar_cli is the tool best suited for distribution through ports to users not necessarily prepared to themselves dig into the code straight away. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-278045-7788-KjRnvge1pA>