Received: from mx1.tetrasec.net (mx1.tetrasec.net [66.245.177.37]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 8AC29782C3A for <~alpine/devel@lists.alpinelinux.org>; Thu, 13 May 2021 10:47:23 +0000 (UTC) Received: from mx1.tetrasec.net (mail.local [127.0.0.1]) by mx1.tetrasec.net (Postfix) with ESMTP id 3CF067C5E0; Thu, 13 May 2021 10:47:22 +0000 (UTC) Received: from ncopa-desktop.lan (67.63.200.37.customer.cdi.no [37.200.63.67]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: alpine@tanael.org) by mx1.tetrasec.net (Postfix) with ESMTPSA id 5848B7C5DF; Thu, 13 May 2021 10:47:21 +0000 (UTC) Date: Thu, 13 May 2021 12:47:15 +0200 From: Natanael Copa To: Paul Zillmann Cc: ~alpine/devel@lists.alpinelinux.org Subject: Re: Packaging YugabyteDB Message-ID: <20210513124715.1c874b97@ncopa-desktop.lan> In-Reply-To: <683fbf70-1ee4-4da8-e76f-45a897f3b8f9@h6g.de> References: <683fbf70-1ee4-4da8-e76f-45a897f3b8f9@h6g.de> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-alpine-linux-musl) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Thu, 13 May 2021 11:29:58 +0200 Paul Zillmann wrote: > Hello, >=20 > YugabyteDB is a cloud native scalable database, comparable to CockroachDB, > which speaks both Postgres and Cassandra Protocols on wire. >=20 > Unlike CockroachDB their code and binaries are licensed under the Apache= =20 > License (1). >=20 > I would like to provide an Aport. > However their build system is unusual. >=20 > The build script forces some compiler wrapper scripts to be in specific=20 > places and also downloads and uses build dependencies either in binary=20 > form or source code, including the compiler itself. >=20 > I'm wondering if this way of handling dependencies is an obstacle for=20 > the Alpine Repositories. > If this is not an obstacle, are there any preferred ways of packaging=20 > this (i.e. leave it to the build script, or package the dependencies,=20 > possibly with a yugabyte- prefix in the package name). >=20 > How would you package this? >=20 > I've also contacted the developers (2). Based on the response from upstream, I wouldn't try package it for alpine at all. They are pretty clear that they want control the exact versions of the dependencies themselves and hey clearly do not want traditional distro style builds: > but I don*t think the answer to that is to use the standard > *configure* approach which picks up whichever versions of libraries > that are present on the host OS. https://forum.yugabyte.com/t/building-system/1049/2 So I'd let them do it their way. Anything else will be an uphill battle. >=20 > - Paul >=20 > 1: https://github.com/yugabyte/yugabyte-db/blob/master/LICENSE.md > 2: https://forum.yugabyte.com/t/building-system/1049