From: "Viorel Munteanu" <ceamac@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: app-text/md4c/
Date: Mon, 30 Jan 2023 10:29:30 +0000 (UTC) [thread overview]
Message-ID: <1675013287.b4265a1c06d775fb5329c1c457607890bdbd7297.ceamac@gentoo> (raw)
commit: b4265a1c06d775fb5329c1c457607890bdbd7297
Author: Nickolas Raymond Kaczynski <nrk <AT> disroot <DOT> org>
AuthorDate: Sun Jan 29 17:23:51 2023 +0000
Commit: Viorel Munteanu <ceamac <AT> gentoo <DOT> org>
CommitDate: Sun Jan 29 17:28:07 2023 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=b4265a1c
app-text/md4c: add snapshot, drop 9999, tidy up
upstream seems to be somewhat inactive - so it will take a while before
a new version is released i'd assume. i don't remember exactly what it
was, but there was some bug in the stable version which is why i added
9999 instead (and why i'm doing a snapshot right now).
also fixes the copyright year, i'm quite sure md4c didn't even exist
back in 1999 :)
Signed-off-by: Nickolas Raymond Kaczynski <nrk <AT> disroot.org>
app-text/md4c/Manifest | 1 +
.../md4c/{md4c-9999.ebuild => md4c-0.4.8_p20220115.ebuild} | 10 +++++++---
2 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/app-text/md4c/Manifest b/app-text/md4c/Manifest
new file mode 100644
index 000000000..0614a29be
--- /dev/null
+++ b/app-text/md4c/Manifest
@@ -0,0 +1 @@
+DIST md4c-0.4.8_p20220115.tar.gz 230786 BLAKE2B a2820563bd2f8094d9b57d1ee4bba629229b789b74b34860b1dfcbd45fffea4a477226ad5e8d9eace52b527c08698223ab9343729e4af605d8f9639166aea106 SHA512 1249e8d9c8aef1d305301c4d71f3d438cb81f0e754d9e3ca15c11bf384be67a112086332f41cfddfa2b89790748da0e7db7e62126dc0d9729846268e0dbee651
diff --git a/app-text/md4c/md4c-9999.ebuild b/app-text/md4c/md4c-0.4.8_p20220115.ebuild
similarity index 70%
rename from app-text/md4c/md4c-9999.ebuild
rename to app-text/md4c/md4c-0.4.8_p20220115.ebuild
index caf6b2562..d0bcf814d 100644
--- a/app-text/md4c/md4c-9999.ebuild
+++ b/app-text/md4c/md4c-0.4.8_p20220115.ebuild
@@ -1,18 +1,22 @@
-# Copyright 1999-2022 Gentoo Authors
+# Copyright 2022-2023 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=8
inherit cmake
-# TODO: enable tests, add stable version and useflag for static lib
+# TODO(NRK):
+# - enable tests
+# - useflag for static lib (?)
if [[ ${PV} == 9999 ]]; then
inherit git-r3
EGIT_REPO_URI="https://github.com/mity/md4c.git"
else
- SRC_URI="https://github.com/mity/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz"
+ COMMIT="e9ff661ff818ee94a4a231958d9b6768dc6882c9"
+ SRC_URI="https://github.com/mity/${PN}/archive/${COMMIT}.tar.gz -> ${P}.tar.gz"
KEYWORDS="~amd64"
+ S="${WORKDIR}/${PN}-${COMMIT}"
fi
DESCRIPTION="C Markdown parser. Fast, SAX-like interface, CommonMark Compliant."
next reply other threads:[~2023-01-30 10:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 10:29 Viorel Munteanu [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-16 6:38 [gentoo-commits] repo/proj/guru:master commit in: app-text/md4c/ Viorel Munteanu
2024-02-27 6:31 Haelwenn Monnier
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=1675013287.b4265a1c06d775fb5329c1c457607890bdbd7297.ceamac@gentoo \
--to=ceamac@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