From: Felipe Contreras <felipe.contreras@gmail.com>
To: David Bremner <david@tethera.net>
Cc: Tomi Ollila <tomi.ollila@iki.fi>, Ali Polatel <alip@exherbo.org>,
notmuch@notmuchmail.org
Subject: Re: Can't compile notmuch-delivery
Date: Fri, 1 Jun 2012 20:44:16 +0200 [thread overview]
Message-ID: <CAMP44s3mHg_bF154QTtMFqs1rx7SLhuZXwsXYScF6bKgcdK5Ag@mail.gmail.com> (raw)
In-Reply-To: <874nqu28y1.fsf@zancas.localnet>
On Fri, Jun 1, 2012 at 8:17 PM, David Bremner <david@tethera.net> wrote:
> Jameson Graef Rollins <jrollins@finestructure.net> writes:
>
>> I don't know, but this is one of the reasons I'm against having
>> "contrib" stuff in the notmuch repo. If it's not part of the stuff
>> we're willing to release in source tarballs or binary packages then it
>> should probably be in a separate repo.
>
> Just to be clear, ./contrib currently is in the source tarballs, and at
> least notmuch-mutt is included in a binary package for debian.
>
> I don't disagree that status is kindof odd, but I don't see the stuff in
> contrib as being that different in practice from the bindings. In both
> cases we have had incidences of bitrot. The python bindings are
> currently not a problem, but both the ruby and go bindings stopped
> working at all recently.
I see these as different issues: ruby bindings not working because of
a change in the ruby bindings is understandable, but ruby bindings not
working because of an API change *and* that nobody bothered to
implement this change would not make sense to me. Maybe ruby
maintainers don't have that much time, which is why they don't make so
many changes; but the bindings still work, and if somebody has the
time to make changes, well, he has the time, but forcing the issue
when breaking API does not make sense.
I don't see why it would be difficult to do the API updates through
all the notmuch code; if we can't update the API through all the code
in a timely manner, how do we hope 3rd party uses would?
If anything it would be an incentive to don't break the API so often;
let's face it, notmuch is not so widely used, and breaking the API is
not going to help things.
Another option is to go the FFmpeg way: create a new function
notmuch_database_open2, mark the old one as deprecated (but still
works), and only after some time obsolete it.
Cheers.
--
Felipe Contreras
next prev parent reply other threads:[~2012-06-01 18:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 21:42 Can't compile notmuch-delivery Jostein Gogstad
2012-06-01 6:44 ` Tomi Ollila
2012-06-01 8:54 ` Felipe Contreras
2012-06-01 13:43 ` David Bremner
2012-06-01 17:01 ` Jameson Graef Rollins
2012-06-01 18:17 ` David Bremner
2012-06-01 18:28 ` Jameson Graef Rollins
2012-06-01 18:46 ` David Bremner
2012-06-01 22:49 ` Justus Winter
2012-06-02 2:14 ` David Bremner
2012-06-01 18:44 ` Felipe Contreras [this message]
2012-06-03 5:35 ` Adam Wolfe Gordon
2012-06-04 7:02 ` Jostein Gogstad
2012-06-04 7:07 ` Jostein Gogstad
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMP44s3mHg_bF154QTtMFqs1rx7SLhuZXwsXYScF6bKgcdK5Ag@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=alip@exherbo.org \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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 public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).