MIME-Version: 1.0
References: <CAGFcrM=KPg5AZie-ux055SVAZu08EmSJ3s-Q_Map5j5CmGaaKA@mail.gmail.com>
 <a3367d7-d3c5-4755-289e-37507033405f@dereferenced.org> <CAGFcrMmSG6RbG_O+NrHZ0Cys=6stLy59JjBsqd=BnfncLXdiCQ@mail.gmail.com>
 <CKWTBZV0CKNR.2S5ZYWZVZ5KDP@sumire>
In-Reply-To: <CKWTBZV0CKNR.2S5ZYWZVZ5KDP@sumire>
From: Tomas Kolda <koldat@gmail.com>
Date: Wed, 22 Jun 2022 18:57:35 +0200
Message-ID: <CAGFcrM=wAegGwYTH5ruGcKX=X2AgYnktG=p+rtgxQCs_w9qdPA@mail.gmail.com>
Subject: Re: Native Alpine GLibc support (NEW)
To: alice <alice@ayaya.dev>
Cc: Ariadne Conill <ariadne@dereferenced.org>, ~alpine/devel@lists.alpinelinux.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

st 22. 6. 2022 v 18:44 odes=C3=ADlatel alice <alice@ayaya.dev> napsal:
> the example patches you have posted on github are very far from no-ops
> at all, they require constant vigilance on how to maintain the
> musl-specific patches to be separate and still work. i don't think
> anyone wants to add musl specific patches as musl && msg && patch -p1,
> and they were all also removed from checksums.
>
Main reason is that abuild does not allow to conditionally exclude
patch as it requires it (build fails as checksum exists for something
not used). So I used this approach (current functionality). Otherwise
a build script would need a tweak like:

sources_exclude=3D.....
or even without condition
sources_exclude_glibc=3D.....

Ofcourse there are many ways of having it nice and current POC is not
final. I first tested if it is possible (it is). Then I tried to ask
if community even would want to do something like that (in
anyacceptable  way).