Github messages for voidlinux
 help / color / mirror / Atom feed
From: Anidetrix <Anidetrix@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: yazi-0.1.5
Date: Sun, 03 Dec 2023 17:45:05 +0100	[thread overview]
Message-ID: <20231203164505.08XccNOWgnOnLW3v_zxWbE0Ad96zTBSE1m2bAykZpkY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46909@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 730 bytes --]

New comment by Anidetrix on void-packages repository

https://github.com/void-linux/void-packages/pull/46909#issuecomment-1837534726

Comment:
yazi uses vendored luajit52 as seen [here](https://github.com/sxyazi/yazi/blob/v0.1.5/plugin/Cargo.toml#L14)

from [mlua README](https://github.com/khvzak/mlua#compiling):
> mlua also supports vendored lua/luajit using the auxiliary crates [lua-src](https://crates.io/crates/lua-src) and [luajit-src](https://crates.io/crates/luajit-src). Just enable the vendored feature and cargo will automatically build and link specified lua/luajit version.

which means yazi will bundle it's own luajit52, so changes to plugin/Cargo.toml and lua52-devel dependency should be removed I believe

  parent reply	other threads:[~2023-12-03 16:45 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26 15:16 [PR PATCH] " Bnyro
2023-10-26 15:18 ` [PR PATCH] [Updated] " Bnyro
2023-10-28 18:54 ` rookiejet
2023-10-29  8:48 ` Bnyro
2023-10-29  8:48 ` Bnyro
2023-10-29 13:00 ` rookiejet
2023-10-29 14:21 ` [PR PATCH] [Updated] " Bnyro
2023-10-29 14:21 ` Bnyro
2023-11-15 17:27 ` realcharmer
2023-12-03 16:43 ` Anidetrix
2023-12-03 16:44 ` Anidetrix
2023-12-03 16:45 ` Anidetrix [this message]
2023-12-03 16:45 ` Anidetrix
2023-12-03 16:48 ` Anidetrix
2023-12-03 17:09 ` Anidetrix
2023-12-03 18:46 ` Bnyro
2023-12-03 18:48 ` Bnyro
2023-12-03 19:05 ` Anidetrix
2023-12-03 19:05 ` Anidetrix
2023-12-03 19:05 ` Anidetrix
2023-12-03 19:11 ` Anidetrix
2023-12-04 14:57 ` [PR PATCH] [Updated] " Bnyro
2023-12-04 15:26 ` Bnyro
2024-01-17 17:39 ` sxyazi
2024-01-17 18:18 ` Bnyro
2024-01-17 18:18 ` [PR PATCH] [Updated] " Bnyro
2024-01-17 18:18 ` Bnyro
2024-01-17 18:24 ` New package: yazi-0.2.1 Anidetrix
2024-01-17 18:24 ` sxyazi
2024-01-17 18:29 ` [PR PATCH] [Updated] " Bnyro
2024-01-17 18:30 ` [PR REVIEW] " Anidetrix
2024-01-17 18:39 ` sxyazi
2024-01-17 18:42 ` [PR PATCH] [Updated] " Bnyro
2024-01-28 17:23 ` LinArcX
2024-02-13 16:19 ` melroy89
2024-02-13 16:20 ` melroy89
2024-02-19 18:42 ` sxyazi
2024-02-19 19:20 ` [PR PATCH] [Updated] " Bnyro
2024-02-19 19:21 ` Bnyro
2024-04-13 23:13 ` New package: yazi-0.2.3 zen0bit
2024-04-14  0:54 ` zen0bit
2024-04-14 10:25 ` [PR PATCH] [Updated] " Bnyro
2024-04-22 14:52 ` [PR REVIEW] New package: yazi-0.2.4 classabbyamp
2024-04-23 13:31 ` [PR PATCH] [Updated] " Bnyro
2024-04-23 13:59 ` toomyem
2024-04-29 15:29 ` New package: yazi-0.2.5 manfred3000
2024-04-29 15:32 ` manfred3000
2024-04-29 16:09 ` sxyazi
2024-06-07  8:00 ` toomyem
2024-06-14  6:55 ` [PR PATCH] [Merged]: " classabbyamp

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=20231203164505.08XccNOWgnOnLW3v_zxWbE0Ad96zTBSE1m2bAykZpkY@z \
    --to=anidetrix@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).