Package Details: khal-git 0.10.6.dev26+gdc6d5a1-1

Git Clone URL: https://aur.archlinux.org/khal-git.git (read-only, click to copy)
Package Base: khal-git
Description: CLI calendar application build around CalDAV (Git)
Upstream URL: https://lostpackets.de/khal/
Licenses: MIT
Conflicts: khal
Provides: khal
Submitter: milouse
Maintainer: whynothugo
Last Packager: whynothugo
Votes: 28
Popularity: 0.000000
First Submitted: 2013-12-11 19:24 (UTC)
Last Updated: 2022-06-27 08:00 (UTC)

Latest Comments

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 Next › Last »

eolianoe commented on 2014-05-27 14:54 (UTC)

Could you change the version to a pkgver function, in order to have the git tags ? And add those lines to have zsh completions (with optdepends), man page, and license : install -Dm 644 misc/__khal "${pkgdir}/usr/share/zsh/site-functions/_khal" install -Dm 644 misc/khal.1 "${pkgdir}/usr/share/man/man1/khal.1" install -Dm 644 doc/parts/license.rst "${pkgdir}/usr/share/licenses/${_gitname}/LICENSE"

smu commented on 2014-05-09 11:36 (UTC)

The current version depends on python2-docopt.

milouse commented on 2014-04-25 09:24 (UTC)

Warning, the last update will BROKE your installation as you MUST config vdirsyncer first. I'll add documentation to the post_install/post_upgrade function ASAP. For now, please refer to https://github.com/geier/khal and https://github.com/untitaker/vdirsyncer Sorry for any problem this update may have caused to your workflow.

untitaker commented on 2014-04-24 19:24 (UTC)

This now depends on python2-vdirsyncer

milouse commented on 2014-04-10 19:58 (UTC)

Done :)

erikw commented on 2014-04-10 19:06 (UTC)

Yup please fix the post_install instructions about the config file path.

PotatoesMaster commented on 2014-04-10 18:19 (UTC)

Thanks for maintaining this. A little something: the config file should be located at ~/.config/khal/khal.conf, not ~/.config/khal.conf as stated by khal.install.

jasonwryan commented on 2014-04-09 20:48 (UTC)

Yes: it makes sense to keep pulling master...

milouse commented on 2014-04-09 13:26 (UTC)

Thanks @jasonwryan for your PKGBUILD. I've updated this package to reflect the change and pulling the last git commit of the master branch. For now I think I'll keep pulling the master branch, as the new vdir branch might be very unstable. Any thougth about it ? By the way, I saw that a "stable" 0.1.0 tag has landed on git, so I'll create another package to distribute the tagged version ASAP and maintain this two channels.