From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 22458@debbugs.gnu.org
Subject: bug#22458: Collision between khal and vdirsyncer "bin/vdirsyncer"
Date: Tue, 3 May 2016 17:48:26 -0400 [thread overview]
Message-ID: <20160503214826.GA14028@jasmine> (raw)
In-Reply-To: <8737pykhyy.fsf@gnu.org>
On Tue, May 03, 2016 at 10:24:37PM +0200, Ludovic Courtès wrote:
> ludo@gnu.org (Ludovic Courtès) skribis:
>
> > Leo Famulari <leo@famulari.name> skribis:
> >
> >> The packages khal and vdirsyncer are meant to be used together. Khal is
> >> a console calendar program and vdirsyncer synchronizes CalDAV data from
> >> a remote server to the local filesystem so that khal can use it.
> >
> > Then why do they both provide the same file? :-)
> >
> >> For some reason, the khal package is creating an
> >> "EASY-INSTALL-ENTRY-SCRIPT" (as "bin/.vdirsyncer-real") that wraps the
> >> propagated vdirsyncer executable. This means that both the khal and
> >> vdirsyncer packages contain the path "bin/vdirsyncer", which is
> >> annoying. Thankfully, they both end up executing the real vdirsyncer.
> >
> > I’m not sure I follow. Does upstream khal explicitly intend to install
> > its own bin/vdirsyncer?
>
> Ping? :-)
Since I filed the bug, I might have learned enough to debug it. I'll
take a look in the next day or so.
next prev parent reply other threads:[~2016-05-03 21:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-24 23:24 bug#22458: Collision between khal and vdirsyncer "bin/vdirsyncer" Leo Famulari
2016-02-03 21:56 ` Ludovic Courtès
2016-05-03 20:24 ` Ludovic Courtès
2016-05-03 21:48 ` Leo Famulari [this message]
2016-12-02 19:20 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160503214826.GA14028@jasmine \
--to=leo@famulari.name \
--cc=22458@debbugs.gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.