Ciaran McCreesh kirjoitti: > On Fri, 09 Nov 2007 23:55:51 +0200 > Petteri Räty <[EMAIL PROTECTED]> wrote: >> Usually it's best that ebuild variables follow the order that is in >> skel.ebuild. So know we should decide where to place EAPI. I suggest >> we put it it after LICENSE as that's where the more technical stuff >> like SLOT starts. Attached a patch for skel.ebuild. > > It needs to go right at the top, before 'inherit'. >
What if I want to use EAPI=1 features in an eclass? So if we for example we have an ebuild using EAPI=2 and then it inherits and eclass that sets EAPI=1 for slot deps. Regards, Petteri
signature.asc
Description: OpenPGP digital signature
