From: "Alexandre Restovtsev" <tetromino@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gnome:master commit in: gnome-extra/gnome-contacts/
Date: Sun, 6 Nov 2011 21:39:20 +0000 (UTC) [thread overview]
Message-ID: <20f04adfb1bb10732ec037c0136f75c49cb93f2e.tetromino@gentoo> (raw)
commit: 20f04adfb1bb10732ec037c0136f75c49cb93f2e
Author: Alexandre Rostovtsev <tetromino <AT> gentoo <DOT> org>
AuthorDate: Sun Nov 6 21:35:44 2011 +0000
Commit: Alexandre Restovtsev <tetromino <AT> gmail <DOT> com>
CommitDate: Sun Nov 6 21:35:44 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/gnome.git;a=commit;h=20f04adf
gnome-extra/gnome-contacts: do not check for valac for tarball releases
Do not check for valac when building from pre-generated C sources;
thanks to Gilles Dartiguelongue for noticing.
---
.../gnome-contacts/gnome-contacts-9999.ebuild | 4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/gnome-extra/gnome-contacts/gnome-contacts-9999.ebuild b/gnome-extra/gnome-contacts/gnome-contacts-9999.ebuild
index 6a81d3d..0c28a95 100644
--- a/gnome-extra/gnome-contacts/gnome-contacts-9999.ebuild
+++ b/gnome-extra/gnome-contacts/gnome-contacts-9999.ebuild
@@ -49,6 +49,8 @@ pkg_setup() {
DOCS="AUTHORS ChangeLog NEWS" # README is empty
# configure checks for valac, but will not use it when building from tarball
if [[ ${PV} = 9999 ]]; then
- G2CONF="${G2CONF} VALAC=$(type -p valac-0.14)"
+ G2CONF="${G2CONF} VALAC=$(type -P valac-0.14)"
+ else
+ G2CONF="${G2CONF} VALAC=$(type -P true)"
fi
}
next reply other threads:[~2011-11-06 21:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 21:39 Alexandre Restovtsev [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-23 20:37 [gentoo-commits] proj/gnome:master commit in: gnome-extra/gnome-contacts/ Mart Raudsepp
2018-05-27 21:50 Gilles Dartiguelongue
2018-05-27 21:50 Gilles Dartiguelongue
2018-03-09 16:10 Sobhan Mohammadpour
2015-05-09 22:25 Gilles Dartiguelongue
2014-12-22 23:11 Gilles Dartiguelongue
2014-11-23 23:24 Gilles Dartiguelongue
2014-04-20 23:44 Gilles Dartiguelongue
2014-04-20 18:17 Gilles Dartiguelongue
2014-02-12 20:58 Gilles Dartiguelongue
2013-12-08 21:46 Gilles Dartiguelongue
2013-11-14 22:52 Gilles Dartiguelongue
2013-06-03 2:41 Alexandre Rostovtsev
2012-12-19 0:55 Alexandre Rostovtsev
2012-12-18 23:32 Gilles Dartiguelongue
2012-11-25 18:03 Gilles Dartiguelongue
2012-10-27 20:58 Gilles Dartiguelongue
2012-10-01 4:00 Alexandre Rostovtsev
2012-09-21 0:27 Nirbheek Chauhan
2012-05-24 9:11 Alexandre Restovtsev
2012-03-29 10:44 Nirbheek Chauhan
2012-03-29 9:46 Nirbheek Chauhan
2012-03-26 8:20 Nirbheek Chauhan
2011-10-23 8:41 Alexandre Restovtsev
2011-10-19 8:24 Alexandre Restovtsev
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=20f04adfb1bb10732ec037c0136f75c49cb93f2e.tetromino@gentoo \
--to=tetromino@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