Chris Gianelloni kirjoitti: > On Sun, 2007-11-11 at 21:01 +0200, Petteri Räty wrote: >> I plan to make the java eclasses use the EAPI 1 > > Any chance we can *at least* wait until we have a release out the door > that has a portage version which supports these features *before* we > start trying to use them in the tree? Our general rule was to not use > features for 1+ years since it was added to a *stable* portage before we > started using them. Now, this isn't so much of an issue with individual > ebuilds, but you're talking about changing how the Java eclasses work, > essentially blocking *anyone* using an older portage (including everyone > installing from 2007.0 media) from using any package which inherits the > eclass.
I took this into consideration from the start. You misunderstood my plans. I don't plan to just stick it globally for all current Java ebuilds as there is nothing in EAPI=1 that would warrant that. You can see my plans in more detail in a later post in this thread. > > Also, we should really think about this sort of thing before we start > using it. How are we going to support EAPI changes in eclasses? As said in this thread you really can't set EAPI in an eclass. Regards, Petteri
signature.asc
Description: OpenPGP digital signature
