From: "Markos Chandras" <hwoarang@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/qt:master commit in: Documentation/maintainers/
Date: Sat, 22 Sep 2012 16:36:40 +0000 (UTC) [thread overview]
Message-ID: <1348331792.6eb7e8cc5ca792f2a558b288f8f6b0c21a6c182d.hwoarang@gentoo> (raw)
commit: 6eb7e8cc5ca792f2a558b288f8f6b0c21a6c182d
Author: Markos Chandras <hwoarang <AT> gentoo <DOT> org>
AuthorDate: Sat Sep 22 16:36:32 2012 +0000
Commit: Markos Chandras <hwoarang <AT> gentoo <DOT> org>
CommitDate: Sat Sep 22 16:36:32 2012 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/qt.git;a=commit;h=6eb7e8cc
compare-ebuilds: Use portageq to get overlay's abs path
---
Documentation/maintainers/compare-ebuilds.sh | 5 +----
1 files changed, 1 insertions(+), 4 deletions(-)
diff --git a/Documentation/maintainers/compare-ebuilds.sh b/Documentation/maintainers/compare-ebuilds.sh
index fb9002e..ba630e9 100644
--- a/Documentation/maintainers/compare-ebuilds.sh
+++ b/Documentation/maintainers/compare-ebuilds.sh
@@ -18,10 +18,7 @@ OVERLAY=
LIVE_VERSION="4.8.9999" # you normally don't need to change that
#hacky way to find full path for qt overlay
-for prof in $(portageq portdir_overlay); do
- grep -q "^qt$" ${prof}/profiles/repo_name
- [[ $? == 0 ]] && OVERLAY=${prof} && break
-done
+OVERLAY=$(portageq get_repo_path / qt)
[[ -z ${OVERLAY} ]] && \
echo "Can't find path for your Qt overlay" && \
next reply other threads:[~2012-09-22 16:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-22 16:36 Markos Chandras [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-28 19:31 [gentoo-commits] proj/qt:master commit in: Documentation/maintainers/ Davide Pesavento
2014-08-10 14:29 Davide Pesavento
2014-08-19 1:07 ` Davide Pesavento
2013-06-30 23:11 Davide Pesavento
2012-10-23 17:54 Markos Chandras
2012-10-16 18:30 Markos Chandras
2012-10-16 18:30 Markos Chandras
2012-10-14 21:30 Davide Pesavento
2012-09-22 16:43 Markos Chandras
2012-09-22 12:01 Markos Chandras
2012-07-12 17:10 Markos Chandras
2012-07-10 17:23 Markos Chandras
2012-07-04 17:55 Markos Chandras
2012-06-23 11:06 Markos Chandras
2012-06-09 8:44 Markos Chandras
2012-06-08 20:24 Markos Chandras
2012-06-08 20:20 Markos Chandras
2012-06-08 20:20 Markos Chandras
2012-05-05 22:14 Markos Chandras
2012-03-29 13:56 Davide Pesavento
2012-03-25 16:46 Markos Chandras
2012-03-24 11:10 Markos Chandras
2012-03-24 11:08 Markos Chandras
2012-03-18 11:03 Markos Chandras
2012-03-18 11:00 Markos Chandras
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=1348331792.6eb7e8cc5ca792f2a558b288f8f6b0c21a6c182d.hwoarang@gentoo \
--to=hwoarang@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