On 04/08/2025 18:20, Rafael Sadowski wrote:
> On Sun Jun 02, 2024 at 03:59:30PM +0200, Sebastien Marie wrote:
>> Sebastien Marie <semarie@kapouay.eu.org> writes:
>>> 3. split the port in several parts (maybe FLAVOR or separated ports):
>>>     - main part : duckdb executable + library without extensions (or
>>>       only minimal set)
>>>     - extension part : build the extensions and install *.duckdb_extension
>>>       files in a system directory
>> I started to explore build duckdb and extensions separately, but an
>> additional problem popup: extensions are checked for a signature (from
>> upstream key). So port build ones doesn't have signature and are, by
>> default, refused to be loaded (user should set `allow_unsigned_extensions`
>> flag to permit the load). From user point of vue, building extensions
>> separately seems to be no go.
>>
>> So I intent to build most extensions statically (in cli and shared
>> library), and don't install static files.
>>
>> Thanks.
>> -- 
>> Sebastien Marie
>>
> Please find attached duckdb-1.3.2. I cleanup a little bit and
> added do-test. I think there is no good solution for the
> extensions.
>
> Rafael
yes please.