public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jeroen Roovers" <jer@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/redo/
Date: Sat, 24 Nov 2018 13:44:23 +0000 (UTC)	[thread overview]
Message-ID: <1543067061.36918ab31e70174f5c5433a2bd65d9d13f62bf05.jer@gentoo> (raw)

commit:     36918ab31e70174f5c5433a2bd65d9d13f62bf05
Author:     Jeroen Roovers <jer <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 24 13:43:51 2018 +0000
Commit:     Jeroen Roovers <jer <AT> gentoo <DOT> org>
CommitDate: Sat Nov 24 13:44:21 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=36918ab3

dev-util/redo: Set BDEPEND

Package-Manager: Portage-2.3.52, Repoman-2.3.12
Signed-off-by: Jeroen Roovers <jer <AT> gentoo.org>

 dev-util/redo/redo-0.21.ebuild  | 2 +-
 dev-util/redo/redo-0.31.ebuild  | 2 +-
 dev-util/redo/redo-99999.ebuild | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/dev-util/redo/redo-0.21.ebuild b/dev-util/redo/redo-0.21.ebuild
index a109d053e05..4c828aa449f 100644
--- a/dev-util/redo/redo-0.21.ebuild
+++ b/dev-util/redo/redo-0.21.ebuild
@@ -13,7 +13,7 @@ SRC_URI="${HOMEPAGE}/archive/${P}.tar.gz"
 LICENSE="LGPL-2"
 SLOT="0"
 KEYWORDS="~amd64 ~hppa ~x86"
-DEPEND="
+BDEPEND="
 	dev-python/beautifulsoup[${PYTHON_USEDEP}]
 	dev-python/markdown[${PYTHON_USEDEP}]
 "

diff --git a/dev-util/redo/redo-0.31.ebuild b/dev-util/redo/redo-0.31.ebuild
index 751f2de294b..cc5f8333e27 100644
--- a/dev-util/redo/redo-0.31.ebuild
+++ b/dev-util/redo/redo-0.31.ebuild
@@ -13,7 +13,7 @@ SRC_URI="${HOMEPAGE}/archive/${P}.tar.gz"
 LICENSE="LGPL-2"
 SLOT="0"
 KEYWORDS="~amd64 ~hppa ~x86"
-DEPEND="
+BDEPEND="
 	dev-python/beautifulsoup[${PYTHON_USEDEP}]
 	dev-python/markdown[${PYTHON_USEDEP}]
 "

diff --git a/dev-util/redo/redo-99999.ebuild b/dev-util/redo/redo-99999.ebuild
index 44c936cb530..574d038e33d 100644
--- a/dev-util/redo/redo-99999.ebuild
+++ b/dev-util/redo/redo-99999.ebuild
@@ -13,7 +13,7 @@ EGIT_REPO_URI="${HOMEPAGE}"
 LICENSE="LGPL-2"
 SLOT="0"
 KEYWORDS=""
-DEPEND="
+BDEPEND="
 	dev-python/beautifulsoup[${PYTHON_USEDEP}]
 	dev-python/markdown[${PYTHON_USEDEP}]
 "


             reply	other threads:[~2018-11-24 13:44 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-24 13:44 Jeroen Roovers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-06 11:41 [gentoo-commits] repo/gentoo:master commit in: dev-util/redo/ Joonas Niilola
2024-11-06 11:41 Joonas Niilola
2022-06-23  5:35 Sam James
2022-06-23  5:35 Sam James
2022-04-17 19:00 Sam James
2022-03-10 21:12 Sam James
2020-07-25 10:22 Michał Górny
2020-06-15  7:31 Jeroen Roovers
2020-03-22 10:09 Jeroen Roovers
2020-03-22 10:09 Jeroen Roovers
2020-02-09 16:25 Michał Górny
2019-12-22  9:48 Jeroen Roovers
2019-12-22  9:36 Jeroen Roovers
2019-12-22  9:36 Jeroen Roovers
2019-09-15  9:01 Jeroen Roovers
2019-08-13 16:13 Michał Górny
2019-08-12 19:52 Michał Górny
2019-07-26  4:46 Jeroen Roovers
2019-07-25  5:38 Jeroen Roovers
2019-06-19  7:31 Jeroen Roovers
2019-01-06 17:44 Jeroen Roovers
2019-01-06 17:44 Jeroen Roovers
2018-11-24 13:33 Jeroen Roovers
2018-11-03 14:04 Jeroen Roovers

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=1543067061.36918ab31e70174f5c5433a2bd65d9d13f62bf05.jer@gentoo \
    --to=jer@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