Brian - Thanks for chiming in here. And thanks for your efforts. (I was able to meet Seemant in India two weeks ago, and he couldn't say enough good about you).
On 12/16/05, Brian Harring <[EMAIL PROTECTED]> wrote: > On Thu, Dec 15, 2005 at 05:51:26PM -0800, m h wrote: > > While I'm firing off questions, any hints as to why there are no > > ebuilds to satisfy bash? (I'm starting through the depgraph code, but > > it is hairy and ugly....) > prefix portage _only_ allows using EAPI="prefix" ebuilds right now. > > Down the line, if prefix is approved/integrated, then an actual EAPI > release will be used instead of the fake one created. > > Either way, why there are no ebuilds is due to portage automatically > filtering out all ebuilds that lack a matching EAPI. > > It's a protection feature, if portage doesn't know of that EAPI level, > it won't allow the user to use it. As far as I understand EAPI is used to define a sort of super class (in OO terms) for an ebuild. (Feel free to correct). I'm using Kito's prefixed ebuilds, which have the line EAPI="prefix" in them. I'm not specifying the overlay right now, but I'm sure there are other environment errors. I'm assumming if I deal with them, this issue will go away. matt -- [email protected] mailing list
