public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-lisp/clisp/
Date: Thu,  3 Jun 2021 19:15:21 +0000 (UTC)	[thread overview]
Message-ID: <1622747687.b3d8d870caaccf6f72588a98bf3d036a13f7b47f.sam@gentoo> (raw)

commit:     b3d8d870caaccf6f72588a98bf3d036a13f7b47f
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Jun  2 23:54:19 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Jun  3 19:14:47 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b3d8d870

dev-lisp/clisp: fix BadDefaultUseFlags

-foo in IUSE is discouraged. It is equivalent (in every meaningful case) to 'foo' but confuses parsing
tools like e.g. packages.gentoo.org.

Dropping '-' from these flags has no impact on the actual default behaviour.

See: https://devmanual.gentoo.org/general-concepts/use-flags/index.html#iuse-defaults
Package-Manager: Portage-3.0.19, Repoman-3.0.3
Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-lisp/clisp/clisp-2.49.92.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-lisp/clisp/clisp-2.49.92.ebuild b/dev-lisp/clisp/clisp-2.49.92.ebuild
index 6a4e241457e..1403a5e81c5 100644
--- a/dev-lisp/clisp/clisp-2.49.92.ebuild
+++ b/dev-lisp/clisp/clisp-2.49.92.ebuild
@@ -12,7 +12,7 @@ SRC_URI="mirror://gentoo/${P}.tar.bz2"
 LICENSE="GPL-2"
 SLOT="2/8"
 KEYWORDS="~alpha amd64 ~ia64 ppc ~sparc x86"
-IUSE="hyperspec X berkdb dbus fastcgi gdbm gtk +pcre postgres +readline svm -threads +unicode +zlib"
+IUSE="hyperspec X berkdb dbus fastcgi gdbm gtk +pcre postgres +readline svm threads +unicode +zlib"
 # "jit" disabled ATM
 
 RDEPEND=">=dev-lisp/asdf-2.33-r3


             reply	other threads:[~2021-06-03 19:15 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03 19:15 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-02  4:32 [gentoo-commits] repo/gentoo:master commit in: dev-lisp/clisp/ 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
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=1622747687.b3d8d870caaccf6f72588a98bf3d036a13f7b47f.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