| 1 |
agreed |
| 2 |
|
| 3 |
> -----Original Message----- |
| 4 |
> From: Alain Penders [mailto:alain@g.o] |
| 5 |
> Sent: Thursday, February 06, 2003 12:38 PM |
| 6 |
> To: gentoo-dev@g.o |
| 7 |
> Subject: Re: [gentoo-dev] portage database management |
| 8 |
> |
| 9 |
> |
| 10 |
> That's indeed the main problem with XML. If you want to see |
| 11 |
> the practicality |
| 12 |
> of this, take a look at Ant (http://ant.apache.org/). Ant is |
| 13 |
> a Java based |
| 14 |
> build system, kinda like Makefiles but WAY more powerful. |
| 15 |
> It's slowly |
| 16 |
> becoming the defacto standard for building Java projects, and |
| 17 |
> especially for |
| 18 |
> large Java projects it's invaluable. |
| 19 |
> |
| 20 |
> It defines a project in XML, and comes with a lot of modules |
| 21 |
> (comparable to |
| 22 |
> eclasses and the default ebuild commands) which can be used |
| 23 |
> inside that XML. |
| 24 |
> |
| 25 |
> Implementing an ebuild in Ant would be very simple, and |
| 26 |
> probably with one or |
| 27 |
> two additional modules one could implement all of portage in |
| 28 |
> ant. Doing the |
| 29 |
> latter would be way slower than portage is today though, and |
| 30 |
> doing the first |
| 31 |
> requires adding Java... not very useful right now either. |
| 32 |
> |
| 33 |
> Looking at the cheer size of Ant -- all the stuff they had to |
| 34 |
> put in before it |
| 35 |
> became a really useful system, I'd vote against trying to do |
| 36 |
> this for portage. |
| 37 |
> Having an XML definition for each package, yes... replacing |
| 38 |
> the actual build |
| 39 |
> code by XML - no. |
| 40 |
> |
| 41 |
> My $0.02... |
| 42 |
> |
| 43 |
> Alain |
| 44 |
> |
| 45 |
> |
| 46 |
> On Thu, Feb 06, 2003 at 03:41:29AM -0600, Jared H. Hudson wrote: |
| 47 |
> > I like XML as much as the next guy, but one thing you |
| 48 |
> should remember |
| 49 |
> > is |
| 50 |
> > that ebuilds are not some arbitrary pkg format -- they're |
| 51 |
> bash scripts. |
| 52 |
> > They may not look it, since they don't have #!/bin/bash at |
| 53 |
> the top, but |
| 54 |
> > they are bash scripts that are sourced with other bash |
| 55 |
> scripts. So, for |
| 56 |
> > example, most ebuilds have bash functins like src_unpack, |
| 57 |
> src_install, |
| 58 |
> > ect, but others have their own functions that are defined |
| 59 |
> and called by |
| 60 |
> > these src_* functions. Converting this to XML would mean |
| 61 |
> that portage |
| 62 |
> > would have to convert everything to bash, plus there'd have |
| 63 |
> to be enough |
| 64 |
> > flexibility in the XML stylesheet we'd to include the |
| 65 |
> possibility of |
| 66 |
> > unknown-ebuild-specific global variables, functions, ect. |
| 67 |
> > |
| 68 |
> > Just food for thought. |
| 69 |
> > |
| 70 |
> > -Jared H. |
| 71 |
> |
| 72 |
> -- |
| 73 |
> gentoo-dev@g.o mailing list |
| 74 |
> |
| 75 |
|
| 76 |
|
| 77 |
-- |
| 78 |
gentoo-dev@g.o mailing list |
Archives