~alpine/devel

1

PKGBUILD conversion script

Details
Message ID
<kj28rB1WsHOJza5spBusM7m8UwoQWNbFcd0tW87AdaXCa5akNSG8N6qCtRZlQeIqeCv-i5dX8fJgFACA3AS6f3Rd-itbfiWNYTOBP67iZb4=@port19.xyz>
DKIM signature
missing
Download raw message
Hi!

I have noticed large similarities between the PKGBUILD format of arch linux and APKGBUILD in alpine.
An awk script converting the two formats may prove beneficial in porting packages.
Of course this has the main limitation of oten differing package names, but that can be disclaimed.
If this sounds like a good idea I can work on an implementation.

Kind Regards,
port19
Details
Message ID
<ZOx4JzsEJH7Tt5sQ@8a493b28811c>
In-Reply-To
<kj28rB1WsHOJza5spBusM7m8UwoQWNbFcd0tW87AdaXCa5akNSG8N6qCtRZlQeIqeCv-i5dX8fJgFACA3AS6f3Rd-itbfiWNYTOBP67iZb4=@port19.xyz> (view parent)
DKIM signature
missing
Download raw message
On Mon, Aug 28, 2023 at 09:11:19AM +0000, port19 wrote:
> Hi!
> 
> I have noticed large similarities between the PKGBUILD format of arch linux and APKGBUILD in alpine.
> An awk script converting the two formats may prove beneficial in porting packages.
> Of course this has the main limitation of oten differing package names, but that can be disclaimed.
> If this sounds like a good idea I can work on an implementation.
> 
> Kind Regards,
> port19

[toAPK][0] is already an existing tool that does already generate
APKBUILDs from PKGBUILDs.

Note that, even though the files look similar, there is still a
difference in packaging policies that you need to take into account as
well, which such tools cannot cover.


[0]:https://gitlab.com/Durrendal/toAPK
Reply to thread Export thread (mbox)