| 1 |
On Thu, 08 Mar 2012 12:48:51 -0500 |
| 2 |
Michael Orlitzky <michael@××××××××.com> wrote: |
| 3 |
> On 03/08/2012 12:28 PM, Michał Górny wrote: |
| 4 |
> > And something will need to provide that /usr/bin/eapi4 thing. And |
| 5 |
> > that introduces new problems: |
| 6 |
> |
| 7 |
> I'm just parroting someone else's suggestion; I don't really know |
| 8 |
> enough about the details to answer these properly. Not that that will |
| 9 |
> stop me. |
| 10 |
|
| 11 |
It probably should. Although in the early days the model for ebuilds |
| 12 |
was that they were scripts that were "executed", nowadays there's so |
| 13 |
much support required that it's better to think of ebuilds as being |
| 14 |
data. If you did have a /usr/bin/eapi5, it would have to be implemented |
| 15 |
as something that invoked the package manager, not as a direct |
| 16 |
interpreter. |
| 17 |
|
| 18 |
-- |
| 19 |
Ciaran McCreesh |
Archives