Package Details: vdirsyncer-git 0.19.1.dev3+g2c44f7d-2

Git Clone URL: https://aur.archlinux.org/vdirsyncer-git.git (read-only, click to copy)
Package Base: vdirsyncer-git
Description: Synchronize CalDAV and CardDAV.
Upstream URL: https://vdirsyncer.readthedocs.org/
Keywords: caldav, calendar, carddav, contacts, sync, vdir
Licenses: BSD
Conflicts: vdirsyncer
Provides: vdirsyncer
Submitter: eolianoe
Maintainer: untitaker
Last Packager: whynothugo
Votes: 8
Popularity: 0.000005
First Submitted: 2016-04-09 11:50 (UTC)
Last Updated: 2022-12-05 11:37 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

whynothugo commented on 2015-04-14 08:04 (UTC)

Please either install /usr/bin/vdirsyncer as /usr/bin/vdirsyncer2, or add conflicts=vdirsyncer. (I'd prefer the former).

eolianoe commented on 2015-02-22 22:03 (UTC)

Maybe README or INSTALL?

untitaker commented on 2015-02-22 22:01 (UTC)

E.g. it's convention to name the changelog either CHANGES, CHANGELOG or NEWS. Is there a similar thing for packaging-related instructions?

eolianoe commented on 2015-02-22 21:57 (UTC)

Ok, I will try to have a look at virtualenv and pip to manage to install the packages needed for tests locally somewhere in ${srcdir}. Sorry, but I did not understand well your question. What are you looking for?

untitaker commented on 2015-02-22 17:43 (UTC)

BTW is there some sort of convention where to store information for package maintainers? Like, a particular filename in the repo root?

untitaker commented on 2015-02-22 17:39 (UTC)

See https://github.com/untitaker/vdirsyncer/blob/master/CONTRIBUTING.rst I wouldn't recommend running the stylechecker though, the errors it reports are not the kind of stuff that should prevent the user from using vdirsyncer.

eolianoe commented on 2015-02-22 17:36 (UTC)

@untitaker: that sounds like a good idea, but how pratically implement this solution? For now it seems that `make test` runs only the test and does not install the package needed for the tests.

untitaker commented on 2015-02-22 10:52 (UTC)

Late to the party, but regarding ``check``, wouldn't it be easier if you create a virtualenv and let pip install the dependencies?

eolianoe commented on 2014-09-23 19:38 (UTC)

@hobarrera: I'm trying to follow as much as possible the GitHub repo, and rebuild regularly the package. I'm ok the add a check function, but I think it's some superfluous dependencies (especially in this case because there is more checkdepends than dependencies ^^). (the same thing apply for your comment at https://aur.archlinux.org/packages/python-vdirsyncer-git/)

whynothugo commented on 2014-09-23 15:01 (UTC)

You should check the package in your PKGBUILD, especially since -git packages have higher chances of breaking: https://aur.archlinux.org/packages/vd/vdirsyncer/PKGBUILD

« First ‹ Previous 1 2 3 4 5 Next › Last »