Petteri Räty kirjoitti:
> 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.
> 
> Regards,
> Petteri
> 

The predominant options seems to be before inherit so let's go with that
then. Will post more details on eclass stuff once I get further with
java stuff.

00:31 < Betelgeuse> zmedico: ping
01:02 < zmedico> Betelgeuse: pong
01:03 < Betelgeuse> zmedico: Haven't seen your thoughts on EAPI place in
ebuild
01:05 < zmedico> I'd say the ebuild should define it before the inherit
01:05 < zmedico> that's the simplest and safest thing to do
01:05 < Betelgeuse> zmedico: ok so I would test for EAPI=1 then in java
eclasses?
01:05 < Betelgeuse> zmedico: And maybe write eapi.eclass for testing
EAPI version
01:06 < Betelgeuse> zmedico: eapi 1 && <do stuff> etc
01:06 < Betelgeuse> If I only need one function then perhaps add it to
eutils
01:06 < zmedico> sure
01:06 < zmedico> yeah

Regards,
Petteri