public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Brian Gloyer" <brian.gloyer@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: app-portage/pacvis/
Date: Wed,  6 Nov 2019 07:41:30 +0000 (UTC)	[thread overview]
Message-ID: <1573025777.7f27e74ceed3cd2c0f76b5d7e52660b790ef3349.brian.gloyer@gentoo> (raw)

commit:     7f27e74ceed3cd2c0f76b5d7e52660b790ef3349
Author:     brian gloyer <brian.gloyer <AT> gmail <DOT> com>
AuthorDate: Wed Nov  6 07:33:45 2019 +0000
Commit:     Brian Gloyer <brian.gloyer <AT> gmail <DOT> com>
CommitDate: Wed Nov  6 07:36:17 2019 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=7f27e74c

app-portage/pacvis: Bump to version 0.4.2

Package-Manager: Portage-2.3.76, Repoman-2.3.16
Signed-off-by: brian gloyer <brian.gloyer <AT> gmail.com>

 app-portage/pacvis/Manifest            |  1 +
 app-portage/pacvis/pacvis-0.4.2.ebuild | 18 ++++++++++++++++++
 2 files changed, 19 insertions(+)

diff --git a/app-portage/pacvis/Manifest b/app-portage/pacvis/Manifest
index 4959bde..bc616a3 100644
--- a/app-portage/pacvis/Manifest
+++ b/app-portage/pacvis/Manifest
@@ -1 +1,2 @@
 DIST pacvis-0.4.1.tar.gz 511582 BLAKE2B 61fe99358b2d1c6f1b500583fa9f4b017ba2548e246c0a4ed2ab59e224e8e8273cfb9c1fdaa233421ce3f45a0e498598b757995c2e74e568450e81cbd44184aa SHA512 146dc13f66c7dcb81f8cbe67461a58df2ea8874c7e4fe97910006b3295c55ce4aa1dff989586a46e2c50ab8156a8dd2519962bf041c54877d1e4de43915ae015
+DIST pacvis-0.4.2.tar.gz 511929 BLAKE2B 3be3dd286caf27b4a27e6ee813db2445262438016def5d14afbeaec70d12ea905fe97cb94b9e19bfc1a12a9560e5647808a5f7e17347db3980f0d308081ce773 SHA512 da86165454845edc229fcd417ceb293402e400caead4ac23f2b8a5c28fd40eea6720c6016092ab5d375d9a756744a7f68a4dbd78431a410dada86048ee188c58

diff --git a/app-portage/pacvis/pacvis-0.4.2.ebuild b/app-portage/pacvis/pacvis-0.4.2.ebuild
new file mode 100644
index 0000000..2e20d84
--- /dev/null
+++ b/app-portage/pacvis/pacvis-0.4.2.ebuild
@@ -0,0 +1,18 @@
+# Copyright 1999-2019 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+PYTHON_COMPAT=( python{3_6,3_7} )
+
+inherit distutils-r1
+
+DESCRIPTION="Displays dependency graphs of packages"
+HOMEPAGE="https://github.com/bgloyer/pacvis.git"
+SRC_URI="https://github.com/bgloyer/pacvis/archive/v${PV}.tar.gz -> ${P}.tar.gz"
+
+LICENSE="MIT"
+SLOT="0"
+KEYWORDS="~amd64"
+IUSE=""
+
+RDEPEND="www-servers/tornado[${PYTHON_USEDEP}]"


             reply	other threads:[~2019-11-06  7:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-06  7:41 Brian Gloyer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-11  6:12 [gentoo-commits] repo/proj/guru:dev commit in: app-portage/pacvis/ Brian Gloyer
2024-04-14  1:39 [gentoo-commits] repo/proj/guru:master " Julien Roy
2024-04-14  1:38 ` [gentoo-commits] repo/proj/guru:dev " Julien Roy
2023-06-12 14:40 Tomas Fabrizio Orsi
2022-06-25  3:01 Brian Gloyer
2021-06-27 20:23 Brian Gloyer
2020-09-07 17:32 Brian Gloyer
2020-06-15  1:32 Brian Gloyer
2020-04-26 22:39 Alessandro Barbieri
2019-10-10  4:16 Brian Gloyer
2019-10-07  6:03 Brian Gloyer
2019-08-30  2:36 Brian Gloyer

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=1573025777.7f27e74ceed3cd2c0f76b5d7e52660b790ef3349.brian.gloyer@gentoo \
    --to=brian.gloyer@gmail.com \
    --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