| 1 |
On Thu, Dec 15, 2005 at 05:51:26PM -0800, m h wrote: |
| 2 |
> While I'm firing off questions, any hints as to why there are no |
| 3 |
> ebuilds to satisfy bash? (I'm starting through the depgraph code, but |
| 4 |
> it is hairy and ugly....) |
| 5 |
prefix portage _only_ allows using EAPI="prefix" ebuilds right now. |
| 6 |
|
| 7 |
Down the line, if prefix is approved/integrated, then an actual EAPI |
| 8 |
release will be used instead of the fake one created. |
| 9 |
|
| 10 |
Either way, why there are no ebuilds is due to portage automatically |
| 11 |
filtering out all ebuilds that lack a matching EAPI. |
| 12 |
|
| 13 |
It's a protection feature, if portage doesn't know of that EAPI level, |
| 14 |
it won't allow the user to use it. |
| 15 |
|
| 16 |
Unless you're using the overlay already, in which case I question if |
| 17 |
portage is actually using the prefix overlay ;) |
| 18 |
~harring |
Archives