public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Eric Joldasov" <bratishkaerik@getgoogleoff.me>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: dev-zig/zls/
Date: Tue, 10 Oct 2023 02:48:39 +0000 (UTC)	[thread overview]
Message-ID: <1696905791.5de3d475f386f7fe7f8d9c23b2e3e5b11dc48dce.bratishkaerik@gentoo> (raw)

commit:     5de3d475f386f7fe7f8d9c23b2e3e5b11dc48dce
Author:     Eric Joldasov <bratishkaerik <AT> getgoogleoff <DOT> me>
AuthorDate: Tue Oct 10 02:43:11 2023 +0000
Commit:     Eric Joldasov <bratishkaerik <AT> getgoogleoff <DOT> me>
CommitDate: Tue Oct 10 02:43:11 2023 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=5de3d475

dev-zig/zls: sync 9999 with latest Zig 9999 changes

Related: https://github.com/ziglang/zig/pull/17392 .

Signed-off-by: Eric Joldasov <bratishkaerik <AT> getgoogleoff.me>

 dev-zig/zls/zls-9999.ebuild | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/dev-zig/zls/zls-9999.ebuild b/dev-zig/zls/zls-9999.ebuild
index fe83830faf..ef9785f27b 100644
--- a/dev-zig/zls/zls-9999.ebuild
+++ b/dev-zig/zls/zls-9999.ebuild
@@ -106,8 +106,7 @@ ezig() {
 src_unpack() {
 	git-r3_src_unpack
 	cd "${S}" || die
-	# "zig build" doesn't have "fetch" subcommand yet
-	ezig build --help || die "Fetching Zig modules failed"
+	ezig build --fetch || die "Fetching Zig modules failed"
 	local ZLS_GEN_FLAGS="--generate-version-data master --generate-version-data-path version_data_offline.zig"
 	ezig build gen --verbose -- ${ZLS_GEN_FLAGS} || die "Pre-generating Zig version data failed"
 }


             reply	other threads:[~2023-10-10  2:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10  2:48 Eric Joldasov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-07 14:51 [gentoo-commits] repo/proj/guru:dev commit in: dev-zig/zls/ Filip Kobierski
2025-04-06 14:00 Eric Joldasov
2025-04-06 13:48 Eric Joldasov
2025-04-05 21:50 Filip Kobierski
2025-04-05 21:14 Filip Kobierski
2025-03-07 14:50 Eric Joldasov
2024-12-27 19:21 Eric Joldasov
2024-12-17 20:59 Eric Joldasov
2024-12-15 12:20 Eric Joldasov
2024-12-15 12:20 Eric Joldasov
2024-08-24 11:16 Eric Joldasov
2024-08-09 17:04 Eric Joldasov
2024-08-07 10:16 Eric Joldasov
2024-08-07 10:15 Eric Joldasov
2024-08-07  9:17 Eric Joldasov
2024-08-07  9:09 Eric Joldasov
2024-08-01  6:25 Eric Joldasov
2024-07-31 19:33 Eric Joldasov
2024-07-31 19:09 Eric Joldasov
2023-08-26 17:01 Eric Joldasov
2023-03-09 14:14 Eric Joldasov
2023-03-09 14:14 Eric Joldasov
2023-03-07  8:43 Eric Joldasov
2023-02-05 11:56 Eric Joldasov
2022-11-04 17:22 Eric Joldasov

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=1696905791.5de3d475f386f7fe7f8d9c23b2e3e5b11dc48dce.bratishkaerik@gentoo \
    --to=bratishkaerik@getgoogleoff.me \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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