Re: [gentoo-dev] A new glep: Ebuild format and metadata handling

2009-06-03 Thread Nirbheek Chauhan
On Thu, Jun 4, 2009 at 6:22 AM, Wyatt Epp wrote: > Okay, this has been bothering mesorry if this is a sort of silly > question, but why not just use the (already extant) metadata.xml for > the...err, metadata about a package? > That's because package-manager critical information cannot be inc

Re: [gentoo-dev] A new glep: Ebuild format and metadata handling

2009-06-03 Thread Wyatt Epp
On Sun, May 31, 2009 at 6:09 PM, Richard Freeman wrote: > > glep55: See GLEP55. To summarize: The eapi is put into the file name so > that the package manager knows the EAPI (and thus how to handle this file > format). While it simplifies the eapi discovery this comes at a high price > as there i

Re: [gentoo-dev] A new glep: Ebuild format and metadata handling

2009-06-03 Thread Michael Haubenwallner
On Sun, 2009-05-31 at 15:56 +0200, Patrick Lauer wrote: Thank you for collecting this up! > parsers: The current practise of putting the eapi definition near the top of > the ebuild, combined with the need to state it for all non-EAPI0 ebuilds, > suggests that it can be parsed without having to s

Re: [gentoo-dev] A new glep: Ebuild format and metadata handling

2009-06-01 Thread Nirbheek Chauhan
On Mon, Jun 1, 2009 at 8:56 PM, Markos Chandras wrote: > I really dont like the idea of changing the file extension in anyway since > .ebuild is something that defines Gentoo. It is like changing .deb for Debian > :P. Somethings must stay untouched. ++ Sentimental value ftw! /me wears asbestos u

Re: [gentoo-dev] A new glep: Ebuild format and metadata handling

2009-06-01 Thread Markos Chandras
> Hello people, > > as the discussion about glep55 has gone in circles long enough I decided to > collect the various ideas presented around that theme complex and compare > them in a way that might allow us to reach a sane decision. > > Since it has become quite a lot of text I've kept some parts

Re: [gentoo-dev] A new glep: Ebuild format and metadata handling

2009-06-01 Thread Thilo Bangert
> glep55: See GLEP55. To summarize: The eapi is put into the file name so > that the package manager knows the EAPI (and thus how to handle this > file format). While it simplifies the eapi discovery this comes at a > high price as there is no reliable way to find and validate all ebuilds. i

Re: [gentoo-dev] A new glep: Ebuild format and metadata handling

2009-05-31 Thread Richard Freeman
Patrick Lauer wrote: If I should have forgotten any approach or misrepresented one I'd appreciate an updated or rephrased section so it can be easily updated. This keeps coming up for some reason: parsers: It enforces some minor limitations, for example EAPI needs to be unique and cannot be

[gentoo-dev] A new glep: Ebuild format and metadata handling

2009-05-31 Thread Patrick Lauer
Hello people, as the discussion about glep55 has gone in circles long enough I decided to collect the various ideas presented around that theme complex and compare them in a way that might allow us to reach a sane decision. Since it has become quite a lot of text I've kept some parts in sentenc