From: "Joonas Niilola" <juippis@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-lang/sassc/
Date: Mon, 18 Jan 2021 14:30:45 +0000 (UTC) [thread overview]
Message-ID: <1610980237.903a8796ef233ffc7ad3c272b6306de47899349e.juippis@gentoo> (raw)
commit: 903a8796ef233ffc7ad3c272b6306de47899349e
Author: David Mudrak <gentoo <AT> mudrd8mz <DOT> net>
AuthorDate: Wed Jan 13 10:30:42 2021 +0000
Commit: Joonas Niilola <juippis <AT> gentoo <DOT> org>
CommitDate: Mon Jan 18 14:30:37 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=903a8796
dev-lang/sassc: Fix missing sassc version number display
When running `sassc --version` the sassc version was displayed as 'na'.
Following the upstream recommendation at
https://github.com/sass/sassc/blob/master/docs/building/unix-instructions.md#manually-building-from-tar-sources-via-github
do the same thing as dev-libs/libsass has been also doing and inject
the version file before building the package.
Package-Manager: Portage-3.0.12, Repoman-3.0.2
Signed-off-by: David Mudrak <gentoo <AT> mudrd8mz.net>
Closes: https://github.com/gentoo/gentoo/pull/19049
Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org>
dev-lang/sassc/sassc-3.6.1.ebuild | 1 +
1 file changed, 1 insertion(+)
diff --git a/dev-lang/sassc/sassc-3.6.1.ebuild b/dev-lang/sassc/sassc-3.6.1.ebuild
index 309816f17dd..82d1a97e118 100644
--- a/dev-lang/sassc/sassc-3.6.1.ebuild
+++ b/dev-lang/sassc/sassc-3.6.1.ebuild
@@ -21,5 +21,6 @@ DOCS=( Readme.md )
src_prepare() {
default
+ [[ -f VERSION ]] || echo "${PV}" > VERSION
eautoreconf
}
next reply other threads:[~2021-01-18 14:30 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 14:30 Joonas Niilola [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-28 4:18 [gentoo-commits] repo/gentoo:master commit in: dev-lang/sassc/ WANG Xuerui
2021-05-22 15:31 Andrew Ammerlaan
2021-05-22 15:10 Sam James
2021-05-22 3:05 Sam James
2021-05-22 1:32 Sam James
2021-03-16 19:23 Sam James
2021-02-19 20:04 Sam James
2021-02-19 12:07 Sam James
2021-02-19 2:41 Sam James
2021-01-12 15:39 Sam James
2020-01-27 19:53 Mart Raudsepp
2019-12-05 7:42 Pacho Ramos
2019-11-19 15:40 Agostino Sarubbo
2019-11-19 7:38 Agostino Sarubbo
2019-11-19 1:31 Aaron Bauman
2019-07-05 19:05 Virgil Dupras
2019-05-28 2:35 Aaron Bauman
2019-05-21 21:51 Virgil Dupras
2019-05-19 21:41 Virgil Dupras
2019-05-19 21:41 Virgil Dupras
2019-03-30 0:12 Virgil Dupras
2019-03-02 19:56 Sergei Trofimovich
2019-02-19 18:05 Andreas Sturmlechner
2018-10-23 22:43 James Le Cuirot
2018-03-23 20:17 Alexandre Rostovtsev
2018-03-23 20:17 Alexandre Rostovtsev
2018-01-29 3:17 Alexandre Rostovtsev
2017-12-28 15:20 Alexandre Rostovtsev
2017-12-28 15:20 Alexandre Rostovtsev
2017-12-26 2:06 Thomas Deutschmann
2017-11-23 18:43 Alexandre Rostovtsev
2017-11-07 8:37 Alexandre Rostovtsev
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=1610980237.903a8796ef233ffc7ad3c272b6306de47899349e.juippis@gentoo \
--to=juippis@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