public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Aaron Swenson" <titanofold@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pygresql/
Date: Sun, 13 May 2018 16:29:29 +0000 (UTC)	[thread overview]
Message-ID: <1526228959.0447e6e3e5f51c5a29ff20f871e3d6851c9ed69f.titanofold@gentoo> (raw)

commit:     0447e6e3e5f51c5a29ff20f871e3d6851c9ed69f
Author:     Aaron W. Swenson <titanofold <AT> gentoo <DOT> org>
AuthorDate: Sun May 13 16:29:19 2018 +0000
Commit:     Aaron Swenson <titanofold <AT> gentoo <DOT> org>
CommitDate: Sun May 13 16:29:19 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0447e6e3

dev-python/pygresql: Cleanup old

Package-Manager: Portage-2.3.24, Repoman-2.3.6

 dev-python/pygresql/Manifest                 |  1 -
 dev-python/pygresql/pygresql-4.1.1-r2.ebuild | 75 ----------------------------
 2 files changed, 76 deletions(-)

diff --git a/dev-python/pygresql/Manifest b/dev-python/pygresql/Manifest
index 398f8c971d4..62d3219b757 100644
--- a/dev-python/pygresql/Manifest
+++ b/dev-python/pygresql/Manifest
@@ -1,2 +1 @@
-DIST PyGreSQL-4.1.1.tgz 100883 BLAKE2B 8b3876803b61fde62a248cf6499b9396a16069fd5cebad8f17ca942990a5502a702081b395745863d54b304d426455dd94d816caea9e09809a7ff0ca1b4903b0 SHA512 4b37c56f2112471aa5f3003a1d867382ce1b7510afa0963f0ceeb2f8175ca601bb5bade9ea2038d44a1041f12233e364f138a635bb7b353d0a82aeb7d9d49b7f
 DIST PyGreSQL-5.0.4.tar.gz 637569 BLAKE2B 3f7bddb8b5e455ca4f181d254d4d125b89a64d7aaa1440b9ab5d916c395b9d93fc9814269992c134b6fd8a81f436752dbe4d7c06125e683a5257361d428c6a6f SHA512 f177ca3b023c007dafe80369b86a1742ff334137e493c3c19ac8bda0181d2543cd2431b8ab8d2d43f30d681121324bc4f236a9ebbddf1e927b071db7c9b34ea6

diff --git a/dev-python/pygresql/pygresql-4.1.1-r2.ebuild b/dev-python/pygresql/pygresql-4.1.1-r2.ebuild
deleted file mode 100644
index c3b79dd202c..00000000000
--- a/dev-python/pygresql/pygresql-4.1.1-r2.ebuild
+++ /dev/null
@@ -1,75 +0,0 @@
-# Copyright 1999-2015 Gentoo Foundation
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=5
-
-POSTGRES_COMPAT=( 9.{0,1,2,3,4,5} )
-PYTHON_COMPAT=( python2_7 )
-
-inherit distutils-r1
-
-MY_P="PyGreSQL-${PV}"
-
-DESCRIPTION="A Python interface for the PostgreSQL database"
-HOMEPAGE="http://www.pygresql.org/"
-SRC_URI="mirror://pypi/P/PyGreSQL/${MY_P}.tgz"
-
-LICENSE="POSTGRESQL"
-SLOT="0"
-KEYWORDS="alpha amd64 hppa ia64 ppc sparc x86"
-IUSE="doc"
-
-DEPEND="|| (
-	dev-db/postgresql:9.5
-	dev-db/postgresql:9.4
-	dev-db/postgresql:9.3
-	dev-db/postgresql:9.2
-	dev-db/postgresql:9.1
-	dev-db/postgresql:9.0
-)"
-
-RDEPEND="${DEPEND}"
-
-S="${WORKDIR}/${MY_P}"
-
-# Verify that the currently selected PostgreSQL slot is set to one of
-# the slots defined in POSTGRES_COMPAT.
-postgres_check_slot() {
-	if ! declare -p POSTGRES_COMPAT &>/dev/null; then
-		die 'POSTGRES_COMPAT not declared.'
-	fi
-
-# Don't die because we can't run postgresql-config during pretend.
-[[ "$EBUILD_PHASE" = "pretend" && -z "$(which postgresql-config 2> /dev/null)" ]] \
-	&& return 0
-
-	local res=$(echo ${POSTGRES_COMPAT[@]} \
-		| grep -c $(postgresql-config show 2> /dev/null) 2> /dev/null)
-
-	if [[ "$res" -eq "0" ]] ; then
-			eerror "PostgreSQL slot must be set to one of: "
-			eerror "    ${POSTGRES_COMPAT[@]}"
-			return 1
-	fi
-
-	return 0
-}
-
-pkg_pretend() {
-	postgres_check_slot
-}
-
-pkg_setup() {
-	postgres_check_slot || die
-}
-
-python_install_all() {
-	local DOCS=( docs/*.txt )
-	distutils-r1_python_install_all
-
-	if use doc; then
-		insinto /usr/share/doc/${PF}/tutorial
-		doins tutorial/*
-		dohtml docs/*.{html,css}
-	fi
-}


             reply	other threads:[~2018-05-13 16:29 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-13 16:29 Aaron Swenson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-04 11:32 [gentoo-commits] repo/gentoo:master commit in: dev-python/pygresql/ Michał Górny
2024-05-04  7:57 Arthur Zamarin
2024-05-04  7:34 Arthur Zamarin
2024-05-04  7:28 Arthur Zamarin
2024-04-20  5:40 Michał Górny
2023-12-02 19:30 Michał Górny
2023-12-02 13:59 Arthur Zamarin
2023-12-02 13:11 Michał Górny
2023-12-02 13:05 Arthur Zamarin
2023-12-02 13:05 Arthur Zamarin
2023-11-09 18:24 Michał Górny
2023-10-25  5:54 Michał Górny
2023-10-24 19:45 Arthur Zamarin
2023-10-24 19:45 Arthur Zamarin
2023-10-24 19:45 Arthur Zamarin
2023-10-04  5:51 Michał Górny
2023-08-28 16:53 Michał Górny
2023-05-03  5:22 Sam James
2022-05-04 17:56 Michał Górny
2022-04-21  8:25 Jakov Smolić
2022-04-21  7:02 Agostino Sarubbo
2022-04-19 17:04 Arthur Zamarin
2022-03-27  9:31 Michał Górny
2022-01-31  7:53 Michał Górny
2021-11-04  8:04 Arthur Zamarin
2021-11-04  8:04 Arthur Zamarin
2021-11-04  8:04 Arthur Zamarin
2021-08-22 21:53 David Seifert
2021-01-24 10:15 Michał Górny
2021-01-20  7:41 Agostino Sarubbo
2021-01-20  0:04 Sam James
2020-12-18 12:29 Aaron W. Swenson
2020-12-01  2:56 Aaron W. Swenson
2020-09-05 15:15 Sam James
2020-09-03 14:29 Thomas Deutschmann
2020-08-14  0:49 Aaron W. Swenson
2020-07-27 20:06 Aaron Bauman
2020-05-11 16:49 Agostino Sarubbo
2020-05-05  6:46 Agostino Sarubbo
2020-03-28 17:44 Michał Górny
2020-01-18 18:48 Michał Górny
2019-06-17 10:36 Aaron W. Swenson
2019-06-15 10:58 Aaron W. Swenson
2019-05-02 21:08 Mikle Kolyada
2019-04-01 19:58 Thomas Deutschmann
2019-03-24 20:12 Sergei Trofimovich
2019-03-24 19:44 Sergei Trofimovich
2019-03-24 10:01 Agostino Sarubbo
2019-02-14 11:34 Aaron W. Swenson
2019-02-14  7:19 Sergei Trofimovich
2018-03-18 20:50 Sergei Trofimovich
2018-03-03 12:14 Tobias Klausmann
2018-02-18 21:05 Sergei Trofimovich
2018-01-05 23:19 Michał Górny
2017-12-30 18:12 Aaron Swenson
2017-12-30 11:02 Sergei Trofimovich
2017-12-29 17:55 Mikle Kolyada
2017-12-19 15:46 Thomas Deutschmann
2017-11-16 21:27 Aaron Swenson
2017-05-02  8:47 Michał Górny
2016-02-19 12:46 Patrick Lauer

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=1526228959.0447e6e3e5f51c5a29ff20f871e3d6851c9ed69f.titanofold@gentoo \
    --to=titanofold@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