public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas Sturmlechner" <asturm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/uriparser/
Date: Sat, 24 Dec 2022 14:49:33 +0000 (UTC)	[thread overview]
Message-ID: <1671893284.a59b9189b2db08bb8ab31bdd5eccf4be4c2351bf.asturm@gentoo> (raw)

commit:     a59b9189b2db08bb8ab31bdd5eccf4be4c2351bf
Author:     Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
AuthorDate: Wed Dec 21 08:07:28 2022 +0000
Commit:     Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
CommitDate: Sat Dec 24 14:48:04 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a59b9189

dev-libs/uriparser: drop 0.9.6

Closes: https://bugs.gentoo.org/887501
Signed-off-by: Andreas Sturmlechner <asturm <AT> gentoo.org>

 dev-libs/uriparser/Manifest               |  1 -
 dev-libs/uriparser/uriparser-0.9.6.ebuild | 57 -------------------------------
 2 files changed, 58 deletions(-)

diff --git a/dev-libs/uriparser/Manifest b/dev-libs/uriparser/Manifest
index 3088bb2227a5..0597d1cbaa0a 100644
--- a/dev-libs/uriparser/Manifest
+++ b/dev-libs/uriparser/Manifest
@@ -1,2 +1 @@
-DIST uriparser-0.9.6.tar.bz2 178888 BLAKE2B 2c7229d8438eaef40657b809742dff7ed8919edfe9b4003be996d967b2d876ec61c6493b60c3a0a167db80365c748ee63f2cebfa04058ae8bed8d29b0ab7ea22 SHA512 c021ab3f93cc0373c9244edafff042c3d73a3904d69e573c277b04ca4a49cd2e88255214599cf433088b32846c9a628dfb116025188a6bb61a40c236827799aa
 DIST uriparser-0.9.7.tar.bz2 179989 BLAKE2B 50d04df0024f2ad926072a06d92066025c12528853e784f28bf311a64eb37b619634fa14265cadf55e514810804adeefb7dea841178f916ccdbd086a897d375b SHA512 7f69c9806665745c1bafe11f818434e27c2da03af387f009ef46c1427af8c008faa45e6f49bece66e0b96fd17b3924ba0af25476e796972c5e4b651f35f74c13

diff --git a/dev-libs/uriparser/uriparser-0.9.6.ebuild b/dev-libs/uriparser/uriparser-0.9.6.ebuild
deleted file mode 100644
index 4bc93db9261e..000000000000
--- a/dev-libs/uriparser/uriparser-0.9.6.ebuild
+++ /dev/null
@@ -1,57 +0,0 @@
-# Copyright 1999-2022 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=7
-
-inherit cmake
-
-DESCRIPTION="Strictly RFC 3986 compliant URI parsing library in C"
-HOMEPAGE="https://uriparser.github.io/"
-SRC_URI="https://github.com/${PN}/${PN}/releases/download/${P}/${P}.tar.bz2"
-
-LICENSE="BSD"
-SLOT="0"
-KEYWORDS="amd64 arm arm64 ppc ~ppc64 sparc x86 ~amd64-linux ~x86-linux ~ppc-macos ~x86-solaris"
-IUSE="+doc qt5 test unicode"  # +doc to address warning RequiredUseDefaults
-
-REQUIRED_USE="qt5? ( doc ) test? ( unicode )"
-RESTRICT="!test? ( test )"
-
-DEPEND="
-	test? ( >=dev-cpp/gtest-1.8.1 )
-"
-BDEPEND="
-	virtual/pkgconfig
-	doc? (
-		>=app-doc/doxygen-1.5.8
-		media-gfx/graphviz
-		qt5? ( dev-qt/qthelp:5 )
-	)
-"
-
-DOCS=( AUTHORS ChangeLog THANKS )
-
-src_configure() {
-	local mycmakeargs=(
-		-DURIPARSER_BUILD_CHAR=ON
-		-DURIPARSER_BUILD_DOCS=$(usex doc ON OFF)
-		-DURIPARSER_BUILD_TESTS=$(usex test ON OFF)
-		-DURIPARSER_BUILD_TOOLS=ON
-		-DURIPARSER_BUILD_WCHAR_T=$(usex unicode ON OFF)
-
-		# The usex wrapper is here to address this warning:
-		#   One or more CMake variables were not used by the project:
-		#   CMAKE_DISABLE_FIND_PACKAGE_Qt5Help
-		$(usex doc "$(cmake_use_find_package qt5 Qt5Help)")
-	)
-	cmake_src_configure
-}
-
-src_install() {
-	cmake_src_install
-
-	if use doc && use qt5; then
-		dodoc "${BUILD_DIR}"/doc/*.qch
-		docompress -x /usr/share/doc/${PF}/${P}.qch
-	fi
-}


             reply	other threads:[~2022-12-24 14:49 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-24 14:49 Andreas Sturmlechner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-01 22:40 [gentoo-commits] repo/gentoo:master commit in: dev-libs/uriparser/ Sam James
2025-01-12 16:33 Jakov Smolić
2025-01-12 16:33 Jakov Smolić
2025-01-12  0:48 Sam James
2025-01-12  0:48 Sam James
2024-05-05 22:14 Sam James
2024-05-05 22:14 Sam James
2024-05-05 22:14 Sam James
2024-05-05 22:14 Sam James
2024-05-05 22:14 Sam James
2024-05-05 22:01 Sam James
2024-05-05 17:24 Sebastian Pipping
2023-11-06 23:48 Sebastian Pipping
2022-12-21  0:24 Sam James
2022-12-20 23:57 Sam James
2022-12-20 23:57 Sam James
2022-12-20 23:57 Sam James
2022-12-20 23:57 Sam James
2022-12-20 23:28 Sam James
2022-11-28 22:41 Sebastian Pipping
2022-10-05 15:01 Sebastian Pipping
2022-01-08 15:02 Sebastian Pipping
2022-01-07 20:10 Arthur Zamarin
2022-01-07 19:52 Arthur Zamarin
2022-01-07 15:30 Sam James
2022-01-07 15:29 Sam James
2022-01-07  0:31 Sam James
2022-01-07  0:31 Sam James
2022-01-06 20:17 Sebastian Pipping
2021-07-15 21:42 Sam James
2021-06-25 14:08 Sebastian Pipping
2021-05-28 12:03 Agostino Sarubbo
2021-05-28 12:02 Agostino Sarubbo
2021-05-27 19:14 Sam James
2021-03-18 18:23 Sebastian Pipping
2021-03-18 17:56 Sebastian Pipping
2021-03-06 18:19 Sebastian Pipping
2021-02-05 15:26 Sergei Trofimovich
2021-01-06 19:34 Fabian Groffen
2020-09-01  0:29 Sam James
2020-08-17 14:07 Agostino Sarubbo
2020-05-31 15:59 Sebastian Pipping
2019-04-28 12:45 Sebastian Pipping
2019-03-28  0:07 Aaron Bauman
2019-03-27 23:44 Thomas Deutschmann
2019-03-27 20:04 Agostino Sarubbo
2019-01-02 17:11 Sebastian Pipping
2018-10-26 23:05 Sebastian Pipping
2018-08-18 11:53 Sebastian Pipping
2018-02-11  0:51 Michael Palimaka
2018-02-11  0:51 Michael Palimaka
2018-02-07 12:05 Sebastian Pipping
2018-02-06 18:36 Thomas Deutschmann
2018-01-28 18:05 Sergei Trofimovich
2018-01-24 20:58 Sebastian Pipping
2018-01-06 16:06 Sebastian Pipping
2017-12-03 22:14 James Le Cuirot
2015-10-13 16:11 Ian Stakenvicius
2015-10-12 15:58 Sebastian Pipping
2015-10-05 16:28 Sebastian Pipping
2015-10-05 16:14 Sebastian Pipping
2015-10-04 21:54 Sebastian Pipping

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=1671893284.a59b9189b2db08bb8ab31bdd5eccf4be4c2351bf.asturm@gentoo \
    --to=asturm@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