public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-emacs/compat/
Date: Tue, 21 Jun 2022 20:38:32 +0000 (UTC)	[thread overview]
Message-ID: <1655843571.a4044d1f67a0038493894d9f68208fa457fa900d.ulm@gentoo> (raw)

commit:     a4044d1f67a0038493894d9f68208fa457fa900d
Author:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Tue Jun 21 20:27:37 2022 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Tue Jun 21 20:32:51 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a4044d1f

app-emacs/compat: Don't die when the installed Emacs doesn't support tests

There's no perfect solution here, but we don't want to override the
user's choice of Emacs' USE flags just for running tests.

Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>

 app-emacs/compat/compat-28.1.1.3.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/app-emacs/compat/compat-28.1.1.3.ebuild b/app-emacs/compat/compat-28.1.1.3.ebuild
index 0f484b68b268..8a61c3a356a2 100644
--- a/app-emacs/compat/compat-28.1.1.3.ebuild
+++ b/app-emacs/compat/compat-28.1.1.3.ebuild
@@ -34,9 +34,9 @@ src_test() {
 		done <<-EOF
 		Your current Emacs version does not support native JSON parsing,
 		which is required for running tests of ${CATEGORY}/${PN}.
-		Use "eselect emacs" to select an Emacs version with such feature.
+		Emerge >=app-editors/emacs-27 with USE="json" and use "eselect emacs"
+		to select that version.
 		EOF
-		die "Unable to run tests, missing \">=app-editors/emacs-27.2[json]\"."
 	else
 		emake test
 	fi


             reply	other threads:[~2022-06-21 20:38 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21 20:38 Ulrich Müller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-19  7:32 [gentoo-commits] repo/gentoo:master commit in: app-emacs/compat/ Arthur Zamarin
2025-02-04 23:21 Sam James
2025-01-06 22:18 Maciej Barć
2024-12-23 17:56 Ulrich Müller
2024-12-23 11:59 Maciej Barć
2024-12-16 23:26 Maciej Barć
2024-09-03 18:32 Jakov Smolić
2024-07-12 12:35 Maciej Barć
2024-05-14 22:21 Maciej Barć
2024-04-23  1:31 Sam James
2024-03-20 19:30 Maciej Barć
2024-01-15 21:20 Maciej Barć
2024-01-03  8:10 Sam James
2023-12-15  2:33 Sam James
2023-11-13 12:38 Maciej Barć
2023-09-10 15:35 Maciej Barć
2023-09-02 15:35 Sam James
2023-08-02 14:11 Maciej Barć
2023-06-24 22:39 Sam James
2023-05-13 14:51 Jakov Smolić
2023-05-13 10:57 Maciej Barć
2023-05-13 10:57 Maciej Barć
2023-04-27 23:32 Sam James
2023-04-02  1:45 Sam James
2023-03-28  0:57 Maciej Barć
2023-03-13 22:48 Sam James
2023-03-13 12:01 Maciej Barć
2023-03-13 12:01 Maciej Barć
2023-03-06 15:33 Maciej Barć
2023-03-06 15:33 Maciej Barć
2023-02-12  0:48 Maciej Barć
2023-02-10 20:36 Sam James
2023-02-08 15:01 Maciej Barć
2023-02-08 15:01 Maciej Barć
2023-02-08 15:01 Maciej Barć
2023-02-02 17:46 Maciej Barć
2023-01-27 13:02 Maciej Barć
2023-01-27 13:02 Maciej Barć
2023-01-27 13:02 Maciej Barć
2023-01-23  7:57 Maciej Barć
2023-01-18 10:30 Maciej Barć
2023-01-16 14:32 Sam James
2023-01-16 12:20 Maciej Barć
2023-01-16 12:20 Maciej Barć
2023-01-09 21:16 Maciej Barć
2023-01-09 21:16 Maciej Barć
2023-01-09 21:16 Maciej Barć
2023-01-06 19:17 Maciej Barć
2023-01-03 23:25 Sam James
2023-01-03 23:25 Sam James
2022-10-17 19:23 Sam James
2022-10-17 17:30 Arthur Zamarin
2022-10-15 14:28 Arthur Zamarin
2022-10-08 20:29 Maciej Barć
2022-10-08 20:29 Maciej Barć
2022-08-27  1:27 Maciej Barć
2022-08-14 20:06 Sam James
2022-07-24 10:52 Matthew Smith
2022-07-24 10:52 Matthew Smith
2022-06-21 20:02 Ulrich Müller
2022-06-21 19:47 Maciej Barć
2022-06-21 19:36 Maciej Barć
2022-06-21 17:48 Maciej Barć
2022-06-21 13:36 Maciej Barć
2022-05-29 14:47 Matthew Smith
2022-05-29  7:41 Matthew Smith

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=1655843571.a4044d1f67a0038493894d9f68208fa457fa900d.ulm@gentoo \
    --to=ulm@gentoo.org \
    --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