To: ~alpine/devel@lists.alpinelinux.org
From: Paul Zillmann <p.zillmann@h6g.de>
Subject: Packaging YugabyteDB
Message-ID: <683fbf70-1ee4-4da8-e76f-45a897f3b8f9@h6g.de>
Date: Thu, 13 May 2021 11:29:58 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.10.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US

Hello,

YugabyteDB is a cloud native scalable database, comparable to CockroachDB,
which speaks both Postgres and Cassandra Protocols on wire.

Unlike CockroachDB their code and binaries are licensed under the Apache 
License (1).

I would like to provide an Aport.
However their build system is unusual.

The build script forces some compiler wrapper scripts to be in specific 
places and also downloads and uses build dependencies either in binary 
form or source code, including the compiler itself.

I'm wondering if this way of handling dependencies is an obstacle for 
the Alpine Repositories.
If this is not an obstacle, are there any preferred ways of packaging 
this (i.e. leave it to the build script, or package the dependencies, 
possibly with a yugabyte- prefix in the package name).

How would you package this?

I've also contacted the developers (2).

- Paul

1: https://github.com/yugabyte/yugabyte-db/blob/master/LICENSE.md
2: https://forum.yugabyte.com/t/building-system/1049