public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andrew Ammerlaan" <andrewammerlaan@riseup.net>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: dev-python/pymdown-extensions/
Date: Sat, 11 Apr 2020 08:15:12 +0000 (UTC)	[thread overview]
Message-ID: <1586592869.0967dec51e36160fa84195b44de7de3b86a6d0d3.andrewammerlaan@gentoo> (raw)
Message-ID: <20200411081512.jN2RmJDurJFq7osNkp7q2OLWyVRMJgRVrM3EWKmcWDU@z> (raw)

commit:     0967dec51e36160fa84195b44de7de3b86a6d0d3
Author:     Andrew Ammerlaan <andrewammerlaan <AT> riseup <DOT> net>
AuthorDate: Sat Apr 11 08:14:29 2020 +0000
Commit:     Andrew Ammerlaan <andrewammerlaan <AT> riseup <DOT> net>
CommitDate: Sat Apr 11 08:14:29 2020 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=0967dec5

dev-python/pymdown-extensions: do not depend on mkdocs-git-rev..

Package-Manager: Portage-2.3.98, Repoman-2.3.22
Signed-off-by: Andrew Ammerlaan <andrewammerlaan <AT> riseup.net>

 .../pymdown-extensions/pymdown-extensions-7.0.0.ebuild       | 12 +++++-------
 1 file changed, 5 insertions(+), 7 deletions(-)

diff --git a/dev-python/pymdown-extensions/pymdown-extensions-7.0.0.ebuild b/dev-python/pymdown-extensions/pymdown-extensions-7.0.0.ebuild
index 71c657c..ccca17b 100644
--- a/dev-python/pymdown-extensions/pymdown-extensions-7.0.0.ebuild
+++ b/dev-python/pymdown-extensions/pymdown-extensions-7.0.0.ebuild
@@ -8,7 +8,6 @@ PYTHON_COMPAT=( python3_{6,7,8} )
 DOCBUILDER="mkdocs"
 DOCDEPEND="
 	dev-python/mkdocs-minify-plugin
-	dev-python/mkdocs-git-revision-date-localized-plugin
 	dev-python/mkdocs-material
 	dev-python/pymdown-lexers
 	dev-python/pyspelling
@@ -36,11 +35,10 @@ DEPEND="test? (
 distutils_enable_tests pytest
 
 python_prepare_all() {
-	# git revision date plugin needs git repo to build
-	if use doc; then
-		git init || die
-		git add -A || die
-		git commit -q -m ".." || die
-	fi
+	# git revision data plugin needs git repo to build
+	# do not depend on this
+	sed -i -e '/git-revision-date-localized/d' \
+		mkdocs.yml || die
+
 	distutils-r1_python_prepare_all
 }


             reply	other threads:[~2020-04-11  8:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-11  8:15 Andrew Ammerlaan [this message]
2020-04-11  8:15 ` [gentoo-commits] repo/proj/guru:master commit in: dev-python/pymdown-extensions/ Andrew Ammerlaan
  -- strict thread matches above, loose matches on Subject: below --
2020-12-07 11:52 Andrew Ammerlaan
2020-12-07 11:52 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-10-22 14:39 Andrew Ammerlaan
2020-04-10  9:56 [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2020-04-10  9:40 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-04-10  7:35 [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2020-04-10  7:25 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-04-09 19:47 [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2020-04-09 17:09 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-03-28 11:08 [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2020-03-28 11:00 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-03-27 17:04 Alessandro Barbieri
2020-03-09 17:07 Andrew Ammerlaan

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=1586592869.0967dec51e36160fa84195b44de7de3b86a6d0d3.andrewammerlaan@gentoo \
    --to=andrewammerlaan@riseup.net \
    --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