From: "Florian Schmaus" <flow@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: dev-util/blueprint-compiler/
Date: Thu, 26 Jan 2023 08:58:58 +0000 (UTC) [thread overview]
Message-ID: <1674685574.29b79fbcf1597d1f6a8d21e95e1e972885936ce3.flow@gentoo> (raw)
commit: 29b79fbcf1597d1f6a8d21e95e1e972885936ce3
Author: Yuan Liao <liaoyuan <AT> gmail <DOT> com>
AuthorDate: Wed Jan 25 22:26:14 2023 +0000
Commit: Florian Schmaus <flow <AT> gentoo <DOT> org>
CommitDate: Wed Jan 25 22:26:14 2023 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=29b79fbc
dev-util/blueprint-compiler: Drop 0.4.0
Signed-off-by: Yuan Liao <liaoyuan <AT> gmail.com>
dev-util/blueprint-compiler/Manifest | 1 -
.../blueprint-compiler-0.4.0.ebuild | 92 ----------------------
2 files changed, 93 deletions(-)
diff --git a/dev-util/blueprint-compiler/Manifest b/dev-util/blueprint-compiler/Manifest
index 1e308fba2..0abec3980 100644
--- a/dev-util/blueprint-compiler/Manifest
+++ b/dev-util/blueprint-compiler/Manifest
@@ -1,2 +1 @@
-DIST blueprint-compiler-v0.4.0.tar.bz2 50396 BLAKE2B eb51af35030fbaa583b809de0449e7e54143a7b5e582b9be24a0345ca704fb1b1d2778d96ebfb02cc66e4c4acdc97a0356e03624f33be1ea28316ed815c0e334 SHA512 9eb3b17e8b44ecd400c1ec683bf1edee54877a0f16e545ba2f9f9cb683163983fd096ff9403ab36658f92678036f4b6b43e1343cf2bc4793332ef4b2972408ac
DIST blueprint-compiler-v0.6.0.tar.bz2 56896 BLAKE2B 318ffa52b2fbf3b07058e5b4d2f9bb0ef1f6614586b79968889921964b454e5c26d44e58a18185263797f7569135662d14471bafd8e501d7c6386e88972193d0 SHA512 458016f4eabef15026cb3ee675111984b19af8a9139bc412dfb48dfef56b0d0ff028316001d0ce04a90b50d6785c92d799f17ed42ca53fc7582345729ae02207
diff --git a/dev-util/blueprint-compiler/blueprint-compiler-0.4.0.ebuild b/dev-util/blueprint-compiler/blueprint-compiler-0.4.0.ebuild
deleted file mode 100644
index 65b53ce6a..000000000
--- a/dev-util/blueprint-compiler/blueprint-compiler-0.4.0.ebuild
+++ /dev/null
@@ -1,92 +0,0 @@
-# Copyright 2022 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=8
-
-PYTHON_COMPAT=( python3_{9..11} )
-
-inherit meson python-r1
-
-if [[ ${PV} == *9999 ]]; then
- inherit git-r3
- EGIT_REPO_URI="https://gitlab.gnome.org/jwestman/blueprint-compiler.git"
-else
- SRC_URI="https://gitlab.gnome.org/jwestman/blueprint-compiler/-/archive/v${PV}/blueprint-compiler-v${PV}.tar.bz2"
- S="${WORKDIR}/${PN}-v${PV}"
- KEYWORDS="~amd64"
-fi
-
-DESCRIPTION="Compiler for Blueprint, a markup language for GTK user interfaces"
-HOMEPAGE="https://jwestman.pages.gitlab.gnome.org/blueprint-compiler/"
-
-LICENSE="LGPL-3+"
-SLOT="0"
-
-IUSE="doc test"
-REQUIRED_USE="${PYTHON_REQUIRED_USE}"
-RESTRICT="!test? ( test )"
-
-BDEPEND="
- ${PYTHON_DEPS}
- doc? (
- dev-python/sphinx[${PYTHON_USEDEP}]
- dev-python/furo[${PYTHON_USEDEP}]
- )
-"
-
-DEPEND="
- test? (
- gui-libs/gtk:4[introspection]
- )
-"
-
-RDEPEND="
- ${PYTHON_DEPS}
-"
-
-src_configure() {
- local emesonargs=(
- $(meson_use doc docs)
- )
- python_foreach_impl meson_src_configure
-}
-
-src_compile() {
- python_foreach_impl meson_src_compile
-}
-
-src_test() {
- python_foreach_impl meson_src_test
-}
-
-src_install() {
- my_src_install() {
- local exe="${ED}/usr/bin/${PN}"
-
- # Meson installs a Python script at ${ED}/usr/bin/${PN}; on
- # Gentoo, the script should go into ${ED}/usr/lib/python-exec,
- # and ${ED}/usr/bin/${PN} should be a symbolic link to
- # ${ED}/usr/lib/python-exec/python-exec2.
- #
- # When multiple PYTHON_TARGETS are enabled, then after the
- # package has been installed for one Python implementation,
- # Meson will follow the ${ED}/usr/bin/${PN} symbolic link and
- # install the script at ${ED}/usr/lib/python-exec/python-exec2
- # for the remaining implementations, leading to file collision.
- if [[ -L "${exe}" ]]; then
- rm -v "${exe}" || die "Failed to remove symbolic link ${exe}"
- fi
-
- meson_src_install
- python_doscript "${exe}"
- python_optimize
-
- # Install Sphinx-generated documentation only once
- # since the documentation is supposed to be identical
- # between different Python implementations
- use doc && HTML_DOCS=( "${BUILD_DIR}/docs"/* )
- }
-
- python_foreach_impl my_src_install
- einstalldocs
-}
next reply other threads:[~2023-01-26 8:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 8:58 Florian Schmaus [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-14 16:35 [gentoo-commits] repo/proj/guru:master commit in: dev-util/blueprint-compiler/ Florian Schmaus
2023-01-26 8:58 Florian Schmaus
2022-12-06 6:09 Viorel Munteanu
2022-12-01 3:59 Haelwenn Monnier
2022-12-01 3:59 Haelwenn Monnier
2022-12-01 3:59 Haelwenn Monnier
2022-12-01 3:59 Haelwenn Monnier
2022-09-17 11:49 Ronny Gutbrod
2022-09-17 11:49 Ronny Gutbrod
2022-08-02 10:55 Haelwenn Monnier
2022-07-07 7:33 Haelwenn Monnier
2022-06-13 10:49 Andrew Ammerlaan
2022-06-13 10:49 Andrew Ammerlaan
2022-06-13 10:49 Andrew Ammerlaan
2022-03-25 11:24 Ronny Gutbrod
2022-02-23 0:33 Ronny Gutbrod
2022-02-20 8:46 Florian Schmaus
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=1674685574.29b79fbcf1597d1f6a8d21e95e1e972885936ce3.flow@gentoo \
--to=flow@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