public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ian Leitch <port001@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Parsing emerge
Date: Fri, 04 Mar 2005 17:52:02 +0000	[thread overview]
Message-ID: <4228A042.4010001@gentoo.org> (raw)
In-Reply-To: <1109948743.11103.33.camel@secures>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chris White wrote:
~ > Well, I do indeed see that as a valid argument, but at the same time,
| something like this may take a bit shorter time as far as implementation
| than getting the works of a new portage API.  In fact, even if we did
| get a portage API, I still think that parsing could extend the
| flexibility of portage as you have you seen.  On another point, I would
| assume (correct me if I'm wrong), that the portage API would be python
| based.  For those who don't want to use python, you can still add
| functionality (this was written in perl) that you desire.

Indeed, it is a nice tool to have while we wait for the API, I should
have made this clear in my first post, sorry :)

As for using other languages, once the API is in place it would then be
possible to create bindings for those languages.

BTW, no need to send to robin.g.o and lists.g.o anymore, either will do.

Regards,
Ian Leitch

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCKKBCefZ4eWAXRGIRAl4kAJ0U5akp5ksMD30nOllbvF9uRxJfxACfSXL1
ykRWHqesC3oxtietmNOjDI4=
=BIVn
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2005-03-04 17:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-04  8:29 [gentoo-dev] Parsing emerge Chris White
2005-03-04 11:08 ` Ian Leitch
2005-03-04 15:05   ` Chris White
2005-03-04 15:05     ` Chris White
2005-03-04 16:19     ` Chris Gianelloni
2005-03-04 17:52     ` Ian Leitch [this message]
2005-03-05  3:03   ` Jason Stubbs
2005-03-05  5:11 ` Chris White
2005-03-06 22:49   ` Aron Griffis

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=4228A042.4010001@gentoo.org \
    --to=port001@gentoo.org \
    --cc=gentoo-dev@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