From: Chris Smith <chris.rs@xtra.co.nz>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Perl interface to portage
Date: Tue, 4 Mar 2003 08:00:11 +0000 [thread overview]
Message-ID: <200303040800.12017.chris.rs@xtra.co.nz> (raw)
In-Reply-To: <20030303181744.GD444@avenger.localdomain>
On Mon, 03 Mar 2003 18:17, Oleg Letsinsky wrote:
> I want the script to be
> more or less universal and "right" - i.e. no hardwired paths, so I need
> the right (i.e. "already existing") way for a perl script to get a
> portage variable - PORTDIR, DISTDIR is enough.
Try parsing the output of "emerge info" its fast and has almost everything you
need in it. Just a quick grep and awk should do it :D
--
Whatever women do they must do twice as well as men to be thought half
as good. Luckily this is not difficult.
-- Charlotte Whitton
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2003-03-03 19:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-02 6:20 [gentoo-dev] Perl interface to portage Oleg Letsinsky
2003-03-02 12:17 ` Mishael Sibiryakov
2003-03-02 12:29 ` Leon Brocard
2003-03-02 17:15 ` Nick Jones
2003-03-02 13:51 ` Alain Penders
2003-03-03 18:17 ` Oleg Letsinsky
2003-03-03 22:18 ` Alain Penders
2003-03-04 8:00 ` Chris Smith [this message]
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=200303040800.12017.chris.rs@xtra.co.nz \
--to=chris.rs@xtra.co.nz \
--cc=gentoo-dev@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