diff options
| author | Tobias Brox <tobias@redpill-linpro.com> | 2020-05-05 15:40:51 +0200 |
|---|---|---|
| committer | Tobias Brox <tobias@redpill-linpro.com> | 2020-05-05 15:40:51 +0200 |
| commit | 7e0ed2c098ec9897d30f30061bbac17913726229 (patch) | |
| tree | e1a757dc433b29322930d6af5c47092b67719cdd /README.md | |
| parent | 0999f2cf3df5279428cac6bc2d6c9ee37a43dc12 (diff) | |
| download | calendar-cli-7e0ed2c098ec9897d30f30061bbac17913726229.zip | |
include installation procedures as part of the README, fixes https://github.com/tobixen/calendar-cli/issues/36
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 3 |
1 files changed, 3 insertions, 0 deletions
@@ -10,6 +10,9 @@ There is another project out there, "Command-line Interface for Google Calendar" There is a "competing" project at https://github.com/geier/khal - you may want to check it out - it's more mature but probably more complex. It's using a "vsyncdir" backend - if I've understood it correctly, that involves building a local copy of the calendar. The philosophy behind calendar-cli is slightly different, calendar-cli is supposed to be a simple cli-based caldav+ical client. No synchronization, no local storage. +Installation +------------ +calendar-cli depends on quite some python libraries, i.e. pytz, caldav, etc. "sudo ./setup.py install" should take care of all those eventually. Support ------- |