From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id iHvVJu+v7F4sCwAA0tVLHw (envelope-from ) for ; Fri, 19 Jun 2020 12:30:39 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id iIqsIu+v7F4dRQAAB5/wlQ (envelope-from ) for ; Fri, 19 Jun 2020 12:30:39 +0000 Received: from arlo.cworth.org (arlo.cworth.org [50.126.95.6]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id E53129404C8 for ; Fri, 19 Jun 2020 12:30:38 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 45EE16DE119D; Fri, 19 Jun 2020 05:30:36 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0UyMmMZNE8tu; Fri, 19 Jun 2020 05:30:35 -0700 (PDT) Received: from arlo.cworth.org (localhost [IPv6:::1]) by arlo.cworth.org (Postfix) with ESMTP id 993596DE10B3; Fri, 19 Jun 2020 05:30:34 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id D113C6DE10B3 for ; Fri, 19 Jun 2020 05:30:33 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tnn2niarD6Sn for ; Fri, 19 Jun 2020 05:30:32 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTP id AF8996DE10B2 for ; Fri, 19 Jun 2020 05:30:32 -0700 (PDT) Received: by fethera.tethera.net (Postfix, from userid 1001) id 46151613A5; Fri, 19 Jun 2020 08:30:32 -0400 (EDT) Received: (nullmailer pid 2182800 invoked by uid 1000); Fri, 19 Jun 2020 12:30:30 -0000 From: David Bremner To: Patrick Totzke , Floris Bruynooghe , Thore Weilbier , notmuch@notmuchmail.org Subject: Re: python/notmuch2 on PyPI In-Reply-To: <159256331872.115863.5343126454368109299@piu> References: <87mu4zcphd.fsf@powell.devork.be> <159256331872.115863.5343126454368109299@piu> Date: Fri, 19 Jun 2020 09:30:30 -0300 Message-ID: <87wo436xw9.fsf@zancas> MIME-Version: 1.0 X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: notmuch-bounces@notmuchmail.org Sender: "notmuch" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 50.126.95.6 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org X-Spam-Score: -0.51 X-TUID: D/KRy8zVs5D6 Patrick Totzke writes: > Hi everyone, > > First off, thanks for your work on notmuch2, Floris! > > Just to clarify: alot does not, and will not, depend on packages being on PyPI > and is not intended to be installed through pip. I simply don't want to provide > support for this. > > This said, I don't think it is difficult to automate pypi uploads and it cannot > hurt to have an "official" release up there instead of several unmaintained > corpses over the years. > > Cheers, > P > Notmuch as a project does not currently distribute any binary packages, whether for linux distros or for PyPi, or fancy new things like flatpaks or snaps. A few of the notmuch developers are also Debian developers, and also maintain notmuch in Debian. We find it convenient to have the source for the Debian packaging in the notmuch repos, and maintain it via the notmuch mail based review process. Other linux distros like Arch, Fedora, and OpenSUSE are maintained by people less involved with upstream development, and they maintain the packaging separately. For me, Pypi packages fall into the same category as other binary packages that I don't use. In principle pypi packages could be maintained the same way Debian packages are. That would require someone knowledgable about the notmuch build system, and about pypi. d