summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTobias Brox <tobias@redpill-linpro.com>2020-05-05 15:40:51 +0200
committerTobias Brox <tobias@redpill-linpro.com>2020-05-05 15:40:51 +0200
commit7e0ed2c098ec9897d30f30061bbac17913726229 (patch)
treee1a757dc433b29322930d6af5c47092b67719cdd
parent0999f2cf3df5279428cac6bc2d6c9ee37a43dc12 (diff)
downloadcalendar-cli-7e0ed2c098ec9897d30f30061bbac17913726229.zip
include installation procedures as part of the README, fixes https://github.com/tobixen/calendar-cli/issues/36
-rw-r--r--INSTALL.md4
-rw-r--r--README.md3
2 files changed, 3 insertions, 4 deletions
diff --git a/INSTALL.md b/INSTALL.md
deleted file mode 100644
index bc67ddf..0000000
--- a/INSTALL.md
+++ /dev/null
@@ -1,4 +0,0 @@
-Installing the calendar-cli
-===========================
-
-"sudo ./setup.py install" should just work \ No newline at end of file
diff --git a/README.md b/README.md
index 14049a1..f4e2b8b 100644
--- a/README.md
+++ b/README.md
@@ -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
-------