From: "Riyad Kalla" <rsk@u.arizona.edu>
To: <gentoo-dev@gentoo.org>
Subject: RE: [gentoo-dev] portage database management
Date: Thu, 6 Feb 2003 15:30:34 -0700 [thread overview]
Message-ID: <002301c2ce2f$5d855880$d628c480@rskwork> (raw)
In-Reply-To: <53710.192.156.214.55.1044570054.squirrel@webmail.lasierra.edu>
come to think of it, I thought it was all python as well....
anybody know why we thought this?
> -----Original Message-----
> From: Brian Friday [mailto:bfriday@lasierra.edu]
> Sent: Thursday, February 06, 2003 3:21 PM
> To: gentoo-dev@gentoo.org
> Subject: Re: [gentoo-dev] portage database management
>
>
>
> <quote who="Alain Penders">
> > Looking at the cheer size of Ant -- all the stuff they had
> to put in
> > before it became a really useful system, I'd vote against
> trying to do
> > this for portage. Having an XML definition for each
> package, yes...
> > replacing the actual build code by XML - no.
>
> I agree as well, the example I gave earlier of a possible XML
> package file was based on my incorrect assumption portage
> was python and not bash based. Not sure why I got that
> impression, especially as I realize all the conf files have
> bash syntax...
>
> My general thought was this: Craft a XML file which clearly
> identifies the sections of the current ebuild system. Once
> this is done (again I was thinking of python or perl here not
> bash) create a wrapper which acts as a transition layer
> between portage and the new package XML file.
>
> Clearly though I don't know enough about portage so please
> forgive my past/current ignorance as I go back and read the manual.
>
> --
> Brian
>
>
>
> --
> gentoo-dev@gentoo.org mailing list
>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-02-06 22:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 7:59 [gentoo-dev] portage database management Brian Friday
2003-02-06 9:41 ` Jared H. Hudson
2003-02-06 19:37 ` Alain Penders
2003-02-06 20:15 ` Riyad Kalla
2003-02-06 22:20 ` Brian Friday
2003-02-06 22:30 ` Riyad Kalla [this message]
2003-02-07 3:37 ` Mario Witt
2003-02-07 6:53 ` Matt Tucker
-- strict thread matches above, loose matches on Subject: below --
2003-01-29 19:38 Ingo Krabbe
2003-02-01 8:37 ` Rendhalver [Peter Brown]
2003-02-01 8:35 ` Ingo Krabbe
2003-02-01 9:16 ` Rendhalver [Peter Brown]
2003-02-01 9:25 ` Ingo Krabbe
2003-02-01 10:17 ` Rendhalver [Peter Brown]
2003-02-01 11:06 ` John Nilsson
2003-02-01 12:35 ` Ingo Krabbe
2003-02-01 15:34 ` Dylan Carlson
2003-02-02 3:29 ` Mark Constable
2003-02-02 5:44 ` Jim Nutt
2003-02-01 15:34 ` Dylan Carlson
2003-02-01 16:02 ` Ingo Krabbe
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='002301c2ce2f$5d855880$d628c480@rskwork' \
--to=rsk@u.arizona.edu \
--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