From: Chris White <chriswhite@gentoo.org> To: gentoo-dev@robin.gentoo.org Cc: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Parsing emerge Date: Sat, 05 Mar 2005 00:05:39 +0900 [thread overview] Message-ID: <1109948743.11103.33.camel@secures> (raw) In-Reply-To: <422841C8.10407@gentoo.org> [-- Attachment #1: Type: text/plain, Size: 1017 bytes --] At 2005-03-04 11:08 +0000 Ian Leitch Wrote: > Sorry to spoil your post Chris, but I think this is just another > testimonial to how badly we all need that portage API (plus the portage > daemon for tools such as Porthole who currently also have to parse > emerge output). This is by no means the first attempt at parsing I've seen. 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. > But hey, nice work in the absence of the API, it does look like the > script has uses. > > Regards, > Ian Leitch [-- Attachment #2: このメッセージにはデジタル署名された部分があります --] [-- Type: application/pgp-signature, Size: 189 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Chris White <chriswhite@gentoo.org> To: gentoo-dev@gentoo.org Cc: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Parsing emerge Date: Sat, 05 Mar 2005 00:05:39 +0900 [thread overview] Message-ID: <1109948743.11103.33.camel@secures> (raw) Message-ID: <20050304150539.ro-bdiGHk-ZIE2V9ek2-C5bj3IWBzWCqsSdziSeJ9HI@z> (raw) In-Reply-To: <422841C8.10407@gentoo.org> [-- Attachment #1: Type: text/plain, Size: 1017 bytes --] At 2005-03-04 11:08 +0000 Ian Leitch Wrote: > Sorry to spoil your post Chris, but I think this is just another > testimonial to how badly we all need that portage API (plus the portage > daemon for tools such as Porthole who currently also have to parse > emerge output). This is by no means the first attempt at parsing I've seen. 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. > But hey, nice work in the absence of the API, it does look like the > script has uses. > > Regards, > Ian Leitch [-- Attachment #2: このメッセージにはデジタル署名された部分があります --] [-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-04 15:40 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 [this message] 2005-03-04 15:05 ` Chris White 2005-03-04 16:19 ` Chris Gianelloni 2005-03-04 17:52 ` Ian Leitch 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=1109948743.11103.33.camel@secures \ --to=chriswhite@gentoo.org \ --cc=gentoo-dev@gentoo.org \ --cc=gentoo-dev@lists.gentoo.org \ --cc=gentoo-dev@robin.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: linkBe 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