| 1 |
On Sunday 17 May 2009 20:39:26 Jorge Manuel B. S. Vicetto wrote: |
| 2 |
> Ulrich Mueller wrote: |
| 3 |
> >>>>>> On Sun, 17 May 2009, Denis Dupeyron wrote: |
| 4 |
> >> |
| 5 |
> >> 2009/5/17 Piotr Jaroszyñski <peper@g.o>: |
| 6 |
> >>> 1. EAPI-suffixed ebuilds (obviously) |
| 7 |
> >>> 2. EAPI in the filename with one-time extension change |
| 8 |
> >>> 3. Easily fetchable EAPI inside the ebuild and one-time extension |
| 9 |
> >>> change |
| 10 |
> > |
| 11 |
> > I'm strongly against 1 and 2 (no need to repeat the old arguments |
| 12 |
> > here), but I could live with 3. |
| 13 |
> |
| 14 |
> I also prefer 3. |
| 15 |
> |
| 16 |
> >> My preference goes to 3 with a .eb extension and EAPI on the first line. |
| 17 |
> > |
| 18 |
> > Make this "the first non-empty non-comment line". |
| 19 |
> |
| 20 |
> As others have commented, we should probably make this the last comment |
| 21 |
> line in the header. Any suggestions for a specific identification string |
| 22 |
> or do we simply use '# EAPI="X"' or use a she-bang '#!/<..> EAPI="X"' ? |
| 23 |
Yeah, this sounds pretty reasonable to me :) |
| 24 |
|
| 25 |
-- |
| 26 |
Markos Chandras (hwoarang) |
| 27 |
Gentoo Linux Developer [KDE/Qt/Sound/Sunrise] |
| 28 |
Web: http://hwoarang.silverarrow.org |
Archives