On Thursday 12 April 2012 15:53:07 Ulrich Mueller wrote:
> There is consensus in the gentoo-pms mailing list that we should
> tighten the rules for the position of the EAPI assignment in ebuilds,
> namely that it should take place in the first non-blank and
> non-comment line.
>
> The devmanual al
There is consensus in the gentoo-pms mailing list that we should
tighten the rules for the position of the EAPI assignment in ebuilds,
namely that it should take place in the first non-blank and
non-comment line.
The devmanual already requires that "if you want to override the EAPI
variable, you h
On Mon, Mar 19, 2012 at 02:36:34PM +1300, Kent Fredric wrote:
> On 19 March 2012 14:12, Steven J Long wrote:
> >
> > As for non-bash ebuilds, I have always agreed with antarus that they should
> > simply use a different extension. Adding a new extension per source language
> > is a *lot* cleaner t
On 19 March 2012 14:12, Steven J Long wrote:
>
> As for non-bash ebuilds, I have always agreed with antarus that they should
> simply use a different extension. Adding a new extension per source language
> is a *lot* cleaner than one per EAPI.
Ok: If we take this notion and enshrine it in stone:
Firstly, wrt probing the ebuild for EAPI=.. I'd just like to point out that
a regex is not required during the scan, and nor is restricting it to the
first N lines, though the latter may be desirable and could trivially
exclude comment and whitespace-only or empty lines.
Ciaran McCreesh wrote:
