| 1 |
On Fri, 21 Dec 2007 09:37:27 -0700 |
| 2 |
Joe Peterson <lavajoe@g.o> wrote: |
| 3 |
> Assuming that the file extension must change to prevent current PMs |
| 4 |
> from trying to parse new format ebuilds (and not require waiting a |
| 5 |
> year or more), I'd be a lot happier seeing it change *once* to a new |
| 6 |
> fixed extension, with the requirement that the new ebuilds are |
| 7 |
> required to contain within them them EAPI. This should future-proof |
| 8 |
> the system. |
| 9 |
|
| 10 |
Only until another source-level change comes along, which will |
| 11 |
hopefully be fairly soon -- eclasses need a good kick in the nuts, for |
| 12 |
example, and that pretty much means a source-level break. |
| 13 |
|
| 14 |
-- |
| 15 |
Ciaran McCreesh |
Archives