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: net-im/bitlbee/
Date: Tue, 23 Aug 2022 05:11:15 +0000 (UTC)	[thread overview]
Message-ID: <1661230278.b2cdfd96e3450154b38fa6b7a62ef42f817c7f5d.sam@gentoo> (raw)

commit:     b2cdfd96e3450154b38fa6b7a62ef42f817c7f5d
Author:     Petr Vaněk <arkamar <AT> atlas <DOT> cz>
AuthorDate: Fri Aug 19 10:54:33 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Aug 23 04:51:18 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b2cdfd96

net-im/bitlbee: remove obsolete xmpp? ( !nss ) requirement

This requirement was basically introduced with 1.2 release in commit [1]
in order to solve https://bugs.gentoo.org/213958#c8 issue (the xmpp use
flag was called jabber back then). The requirement was later transformed
to REQUIRED_USE in commit [2]. However, this requirement seems no longer
be valid.

The nss use description in metadata was also bogus, it is changed to
more generic form.

[1] https://gitweb.gentoo.org/repo/gentoo/historical.git/commit/?id=30a0fafed3bd420fdb03e6e0a0da3d5f0a86b62e
[2] https://gitweb.gentoo.org/repo/gentoo/historical.git/commit/?id=65aa90800da80b1fbffc36c7b15c3503c37d7fd0

Bug: https://bugs.gentoo.org/213958
Signed-off-by: Petr Vaněk <arkamar <AT> atlas.cz>
Signed-off-by: Sam James <sam <AT> gentoo.org>

 net-im/bitlbee/bitlbee-3.6-r2.ebuild | 1 -
 net-im/bitlbee/bitlbee-3.6-r3.ebuild | 1 -
 net-im/bitlbee/bitlbee-9999.ebuild   | 1 -
 net-im/bitlbee/metadata.xml          | 2 +-
 4 files changed, 1 insertion(+), 4 deletions(-)

diff --git a/net-im/bitlbee/bitlbee-3.6-r2.ebuild b/net-im/bitlbee/bitlbee-3.6-r2.ebuild
index 4c086510b8d5..26f201ce42fd 100644
--- a/net-im/bitlbee/bitlbee-3.6-r2.ebuild
+++ b/net-im/bitlbee/bitlbee-3.6-r2.ebuild
@@ -29,7 +29,6 @@ REQUIRED_USE="
 	|| ( purple xmpp )
 	purple? ( plugins )
 	test? ( xmpp )
-	xmpp? ( !nss )
 "
 
 COMMON_DEPEND="

diff --git a/net-im/bitlbee/bitlbee-3.6-r3.ebuild b/net-im/bitlbee/bitlbee-3.6-r3.ebuild
index 6e4406af9f57..01b8a33d3618 100644
--- a/net-im/bitlbee/bitlbee-3.6-r3.ebuild
+++ b/net-im/bitlbee/bitlbee-3.6-r3.ebuild
@@ -29,7 +29,6 @@ REQUIRED_USE="
 	|| ( purple xmpp )
 	purple? ( plugins )
 	test? ( xmpp )
-	xmpp? ( !nss )
 "
 
 COMMON_DEPEND="

diff --git a/net-im/bitlbee/bitlbee-9999.ebuild b/net-im/bitlbee/bitlbee-9999.ebuild
index 58c3144ff8d5..8d4f88ddc3d1 100644
--- a/net-im/bitlbee/bitlbee-9999.ebuild
+++ b/net-im/bitlbee/bitlbee-9999.ebuild
@@ -29,7 +29,6 @@ REQUIRED_USE="
 	|| ( purple xmpp )
 	purple? ( plugins )
 	test? ( xmpp )
-	xmpp? ( !nss )
 "
 
 COMMON_DEPEND="

diff --git a/net-im/bitlbee/metadata.xml b/net-im/bitlbee/metadata.xml
index 9dbb1759075c..0541d2f03527 100644
--- a/net-im/bitlbee/metadata.xml
+++ b/net-im/bitlbee/metadata.xml
@@ -11,7 +11,7 @@
 	</maintainer>
 	<use>
 		<flag name="libevent">Use libevent for event handling</flag>
-		<flag name="nss">Use NSS for SSL support in Jabber</flag>
+		<flag name="nss">Prefer <pkg>dev-libs/nss</pkg> as SSL/TLS provider</flag>
 		<flag name="otr">Enable support for encrypted conversations</flag>
 		<flag name="plugins">Enable support for plugins</flag>
 		<flag name="purple">Use libpurple instead of the built-in IM protocol support</flag>


             reply	other threads:[~2022-08-23  5:11 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23  5:11 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-27 19:08 [gentoo-commits] repo/gentoo:master commit in: net-im/bitlbee/ Petr Vaněk
2024-02-20  9:08 Petr Vaněk
2024-02-20  9:08 Petr Vaněk
2022-09-30 15:24 Agostino Sarubbo
2022-09-30 15:23 Agostino Sarubbo
2022-09-30 15:22 Agostino Sarubbo
2022-08-30  8:48 Jakov Smolić
2022-08-23  5:11 Sam James
2022-08-23  5:11 Sam James
2022-08-18  7:06 Joonas Niilola
2022-07-28  7:10 Sam James
2022-07-09  9:55 Sam James
2022-06-21 16:12 Jakov Smolić
2022-02-07 20:20 Arthur Zamarin
2022-02-07 20:20 Arthur Zamarin
2022-02-07 20:20 Arthur Zamarin
2021-05-02 19:40 Mikle Kolyada
2021-04-15  8:41 Joonas Niilola
2021-03-26 15:55 Sam James
2020-09-07  8:20 Sergei Trofimovich
2020-08-22 11:26 Agostino Sarubbo
2020-08-22  5:50 Agostino Sarubbo
2020-05-05  8:47 Joonas Niilola
2020-05-05  8:47 Joonas Niilola
2020-05-05  8:47 Joonas Niilola
2020-05-05  8:47 Joonas Niilola
2020-05-05  8:46 Joonas Niilola
2019-11-20 14:39 Joonas Niilola
2019-11-18  5:27 Tim Harder
2019-09-15 14:55 Michał Górny
2019-09-15 14:55 Michał Górny
2019-08-14 23:17 Tim Harder
2017-09-11  6:44 Tim Harder
2017-02-12 15:44 Agostino Sarubbo
2017-02-08  2:12 Michael Weber
2017-02-01 22:32 Tim Harder
2017-01-25  6:30 Tim Harder
2017-01-25  6:30 Tim Harder
2017-01-04 17:09 Agostino Sarubbo
2016-12-21 11:28 Tobias Klausmann
2016-08-07  6:52 Pacho Ramos
2016-07-03 23:01 Zac Medico
2016-03-27  1:26 Tim Harder
2016-03-27  1:26 Tim Harder
2016-03-16 11:51 Agostino Sarubbo
2016-03-15 15:27 Agostino Sarubbo
2016-03-06 12:58 Agostino Sarubbo
2016-01-18  3:33 Tim Harder
2016-01-18  3:17 Tim Harder
2016-01-17 22:20 Tim Harder

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=1661230278.b2cdfd96e3450154b38fa6b7a62ef42f817c7f5d.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