From 10e8ef2d6497baf4dbbac51617dc603c23bb7bf0 Mon Sep 17 00:00:00 2001 From: Felipe Contreras Date: Fri, 1 Jun 2012 20:44:16 +0200 Subject: [PATCH] Re: Can't compile notmuch-delivery --- 6c/4f441010a4b170db0aee2b4c736638ef0c25bc | 111 ++++++++++++++++++++++ 1 file changed, 111 insertions(+) create mode 100644 6c/4f441010a4b170db0aee2b4c736638ef0c25bc diff --git a/6c/4f441010a4b170db0aee2b4c736638ef0c25bc b/6c/4f441010a4b170db0aee2b4c736638ef0c25bc new file mode 100644 index 000000000..4886c3ad6 --- /dev/null +++ b/6c/4f441010a4b170db0aee2b4c736638ef0c25bc @@ -0,0 +1,111 @@ +Return-Path: +X-Original-To: notmuch@notmuchmail.org +Delivered-To: notmuch@notmuchmail.org +Received: from localhost (localhost [127.0.0.1]) + by olra.theworths.org (Postfix) with ESMTP id 7FF93431FBC + for ; Fri, 1 Jun 2012 11:44:18 -0700 (PDT) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Spam-Flag: NO +X-Spam-Score: -0.799 +X-Spam-Level: +X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5 + tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, + FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled +Received: from olra.theworths.org ([127.0.0.1]) + by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) + with ESMTP id kdEV5RYEPbw1 for ; + Fri, 1 Jun 2012 11:44:18 -0700 (PDT) +Received: from mail-lpp01m010-f53.google.com (mail-lpp01m010-f53.google.com + [209.85.215.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) + (No client certificate requested) + by olra.theworths.org (Postfix) with ESMTPS id C252C431FAF + for ; Fri, 1 Jun 2012 11:44:17 -0700 (PDT) +Received: by lagu2 with SMTP id u2so1928834lag.26 + for ; Fri, 01 Jun 2012 11:44:16 -0700 (PDT) +DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; + h=mime-version:in-reply-to:references:date:message-id:subject:from:to + :cc:content-type:content-transfer-encoding; + bh=GpaWv42TeYDF+bXBYoG0sjtrJ4O/3TDDFXwu52Ly0z8=; + b=gR+zzXMBjdmV+kIruYKx7y/qgtCObj+jP9zR8KvM9338KLY0dZRrpz2udoasr9lEje + 56dAJrNvXaU309f2xTjNkXh8n524gT/FQn7Jp2+m0GyyAnUStTyJAt6yQBR2ibHgJYvt + XsGFUCNmi/KrN67GlCbQzK4VwR1haLBDYF82g990ag2wMyBrkcNycu7elIUWBa5lsRZe + XFiz+mYqGP7bZdn/iIif9VpVXCgLFPHNl3RxqJIkExEfFtGrd29b4N6MOdGK0Mxfccus + DvoFklFDAbENZc/KGwKoZbYwmvlh4qH/qj/II2Al4a0hQ21ie5x9KEqPD3/Odh1wH3gi + GFmA== +MIME-Version: 1.0 +Received: by 10.152.123.244 with SMTP id md20mr4186288lab.0.1338576256096; + Fri, 01 Jun 2012 11:44:16 -0700 (PDT) +Received: by 10.112.107.65 with HTTP; Fri, 1 Jun 2012 11:44:16 -0700 (PDT) +In-Reply-To: <874nqu28y1.fsf@zancas.localnet> +References: <20120531214259.GA18272@desktop> + + + <87lik7171d.fsf@zancas.localnet> + <87sjefufub.fsf@servo.finestructure.net> + <874nqu28y1.fsf@zancas.localnet> +Date: Fri, 1 Jun 2012 20:44:16 +0200 +Message-ID: + +Subject: Re: Can't compile notmuch-delivery +From: Felipe Contreras +To: David Bremner +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: quoted-printable +Cc: Tomi Ollila , Ali Polatel , + notmuch@notmuchmail.org +X-BeenThere: notmuch@notmuchmail.org +X-Mailman-Version: 2.1.13 +Precedence: list +List-Id: "Use and development of the notmuch mail system." + +List-Unsubscribe: , + +List-Archive: +List-Post: +List-Help: +List-Subscribe: , + +X-List-Received-Date: Fri, 01 Jun 2012 18:44:18 -0000 + +On Fri, Jun 1, 2012 at 8:17 PM, David Bremner wrote: +> Jameson Graef Rollins writes: +> +>> I don't know, but this is one of the reasons I'm against having +>> "contrib" stuff in the notmuch repo. =C2=A0If 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. + +--=20 +Felipe Contreras -- 2.26.2