From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-lisp/clisp/
Date: Mon, 28 Apr 2025 04:37:16 +0000 (UTC) [thread overview]
Message-ID: <1745815003.90e8aa24f12df6147d76c5d961faab72b0bd8706.sam@gentoo> (raw)
commit: 90e8aa24f12df6147d76c5d961faab72b0bd8706
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Apr 28 04:36:43 2025 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Apr 28 04:36:43 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=90e8aa24
dev-lisp/clisp: further style tweaks
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-lisp/clisp/clisp-2.49.92-r2.ebuild | 15 +++++++++------
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/dev-lisp/clisp/clisp-2.49.92-r2.ebuild b/dev-lisp/clisp/clisp-2.49.92-r2.ebuild
index 59fa721a7fbe..dce4f2773aff 100644
--- a/dev-lisp/clisp/clisp-2.49.92-r2.ebuild
+++ b/dev-lisp/clisp/clisp-2.49.92-r2.ebuild
@@ -19,16 +19,19 @@ RESTRICT="test"
RDEPEND="
>=dev-lisp/asdf-2.33-r3
- virtual/libcrypt:=
- virtual/libiconv
>=dev-libs/libsigsegv-2.10
>=dev-libs/ffcall-1.10
+ virtual/libcrypt:=
+ virtual/libiconv
dbus? ( sys-apps/dbus )
fastcgi? ( dev-libs/fcgi )
- gdbm? ( sys-libs/gdbm:0= )
- gtk? ( >=x11-libs/gtk+-2.10:2 >=gnome-base/libglade-2.6 )
+ gdbm? ( sys-libs/gdbm:= )
+ gtk? (
+ >=gnome-base/libglade-2.6
+ >=x11-libs/gtk+-2.10:2
+ )
postgres? ( >=dev-db/postgresql-8.0:* )
- readline? ( >=sys-libs/readline-7.0:0= )
+ readline? ( >=sys-libs/readline-7.0:= )
pcre? ( dev-libs/libpcre:3 )
svm? ( sci-libs/libsvm )
zlib? ( sys-libs/zlib )
@@ -44,7 +47,7 @@ BDEPEND="X? ( x11-misc/imake )"
PATCHES=(
"${FILESDIR}"/${P}-after_glibc_cfree_bdb.patch
- "${FILESDIR}"/"${P}"-gdbm_and_bdb5.3.patch
+ "${FILESDIR}"/${P}-gdbm_and_bdb5.3.patch
)
BUILDDIR="builddir"
next reply other threads:[~2025-04-28 4:37 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 4:37 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-28 4:44 [gentoo-commits] repo/gentoo:master commit in: dev-lisp/clisp/ Sam James
2025-04-28 2:41 Sam James
2025-04-27 23:17 Sam James
2024-05-02 4:32 Sam James
2024-05-02 4:32 Sam James
2023-09-16 14:06 Ulrich Müller
2022-10-15 15:13 Sam James
2022-05-14 21:52 Jakov Smolić
2022-04-28 15:05 Jakov Smolić
2022-02-28 5:04 Sam James
2022-02-28 5:03 Sam James
2022-02-17 11:00 Jakov Smolić
2022-01-19 1:12 Sam James
2021-06-03 19:15 Sam James
2020-10-10 17:55 Pacho Ramos
2019-06-16 18:30 Ulrich Müller
2019-06-16 17:15 Tobias Klausmann
2019-06-14 15:01 Agostino Sarubbo
2019-06-14 9:26 Agostino Sarubbo
2019-06-14 9:25 Agostino Sarubbo
2019-06-14 9:18 Agostino Sarubbo
2018-10-16 9:18 Tobias Klausmann
2018-08-19 22:52 Patrice Clement
2018-08-19 22:52 Patrice Clement
2018-05-12 0:32 Matt Turner
2018-04-20 8:02 David Seifert
2018-03-28 14:47 José María Alonso
2018-03-25 1:30 Sergei Trofimovich
2018-03-18 18:04 David Seifert
2018-03-08 9:29 José María Alonso
2018-03-07 12:45 José María Alonso
2018-03-07 9:36 José María Alonso
2018-03-06 15:35 José María Alonso
2018-03-05 17:21 José María Alonso
2018-03-05 16:17 José María Alonso
2017-10-25 13:53 Andreas Hüttel
2017-10-24 18:47 Andreas Hüttel
2016-12-18 4:54 Andrey Grozin
2016-10-12 18:11 Pacho Ramos
2016-10-02 2:55 Andrey Grozin
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=1745815003.90e8aa24f12df6147d76c5d961faab72b0bd8706.sam@gentoo \
--to=sam@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