Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m0RPB-0001Ma-OV for pgsql-pkg-debian@arkaria.postgresql.org; Mon, 05 Jul 2021 16:25:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1m0RPA-0007iH-Mi for pgsql-pkg-debian@arkaria.postgresql.org; Mon, 05 Jul 2021 16:25:08 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m0RPA-0007i9-Hx for pgsql-pkg-debian@lists.postgresql.org; Mon, 05 Jul 2021 16:25:08 +0000 Received: from feynman.df7cb.de ([195.49.152.168]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m0RP7-00052V-Tw for pgsql-pkg-debian@postgresql.org; Mon, 05 Jul 2021 16:25:08 +0000 Received: from msg.df7cb.de (unknown [IPv6:2a02:908:1478:7c00:9124:bacd:1e4a:f5a]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-384) server-digest SHA384) (Client did not present a certificate) by feynman.df7cb.de (Postfix) with ESMTPSA id 4GJWHg3NnVz3Dx6; Mon, 5 Jul 2021 18:25:03 +0200 (CEST) Date: Mon, 5 Jul 2021 18:25:03 +0200 From: Christoph Berg To: Andrey Borodin Cc: pgsql-pkg-debian@postgresql.org Subject: Re: Adding packages fro WAL-G and Odyssey Message-ID: Mail-Followup-To: Christoph Berg , Andrey Borodin , pgsql-pkg-debian@postgresql.org References: <5FDAF3A4-4C0D-47F5-821F-20CFD578B3C6@yandex-team.ru> <54DCFC65-56DE-43AE-8219-B9D19B5AA311@yandex-team.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54DCFC65-56DE-43AE-8219-B9D19B5AA311@yandex-team.ru> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Re: Andrey Borodin > > we'd need a proper debian/ directory for these, either in the upstream > > repo or in a separate one. > Odyssey had debian/ dir https://github.com/yandex/odyssey/tree/master/scripts/debian Hi, that directory would need to be /debian, not somewhere deeper in the tree. (Interestingly, you already have a /debian, just with less files.) > WAL-G is simply one Go binary. https://github.com/wal-g/wal-g/tree/master/cmd/pg > Though it's a separate Go binary for each DB: PG, MySQL, MSSQL, MongoDB etc. But I think it's better to start from PG anyway. > We used to build this binary and create almost empty debian/ dir with a script (FPA). We can commit this dir it it's better to have it in source tree. FPA usually doesn't produce "proper" packages with a curated debian/changelog (no throwing away of old entries, and sensible log messages) and the other bits. debian/rules shouldn't try to build a -dbg package these days debian/control shouldn't depend on postgresql-server-dev-13 but on postgresql-server-dev-all if you really need server headers instead of just the client ones. The Description needs more content Standards-Version is outdated Consider using debhelper-compat (= 13) instead of debian/compat 9 Consider providing a systemd .service file along the init script Christoph