From: Bnyro <Bnyro@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: bun-0.5.9
Date: Mon, 01 May 2023 11:55:28 +0200 [thread overview]
Message-ID: <20230501095528.r1g0RWilJWPP50qfSutjedQpVZucXEtlaufMVFwuISU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43681@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 917 bytes --]
New comment by Bnyro on void-packages repository
https://github.com/void-linux/void-packages/pull/43681#issuecomment-1529530832
Comment:
Zig releases new versions every 6 month or so while Bun almost each month. So that way we would always miss around 5 versions until we can update it again. Also, we'd need to find out the Bun release that corresponds nearly to the current zig version, which would be a pita.
Considering the second option, I don't think we can easily figure out which zig version has been used for the Bun release. Apart from that I don't feel like it's a good practice if every package would compile its dependencies itself as that's very time intensive on server side.
In general, what would be the point of building it on our own? Are there any obvious benefits from that? Since the build process seems to be very complicated, I wonder whether the efforts would be any worth it in the end.
next prev parent reply other threads:[~2023-05-01 9:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-30 10:45 [PR PATCH] " Bnyro
2023-04-30 11:41 ` atk
2023-04-30 15:02 ` icp1994
2023-04-30 16:17 ` atk
2023-04-30 18:18 ` Bnyro
2023-04-30 19:43 ` atk
2023-05-01 9:55 ` Bnyro [this message]
2023-05-01 13:52 ` atk
2023-05-01 13:58 ` Bnyro
2023-05-01 13:58 ` Bnyro
2023-05-01 14:27 ` paper42
2023-05-01 15:32 ` atk
2023-05-01 15:37 ` atk
2023-05-05 9:18 ` atk
2023-05-05 14:38 ` Bnyro
2023-05-05 14:39 ` Bnyro
2023-05-08 13:14 ` [PR PATCH] [Updated] " Bnyro
2023-05-08 13:15 ` Bnyro
2023-06-01 13:00 ` [PR PATCH] [Closed]: " Bnyro
2023-06-01 13:02 ` Bnyro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230501095528.r1g0RWilJWPP50qfSutjedQpVZucXEtlaufMVFwuISU@z \
--to=bnyro@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).