On 21/02/10 06:47, Donnie Berkholz wrote: > On 16:51 Thu 21 Jan , Denis Dupeyron wrote: >> On Thu, Jan 21, 2010 at 3:16 PM, Johan Hattne >> <[email protected]> wrote: >>> Great! Any reference on that? The prefix list (or gentoo-alt, rather) >>> has been remarkably silent on the issue, and >> >> You can check the council meeting summary of last month where prefix >> is approved pending some final actions [1], and this month's meeting >> log (the summary should make it to the page any time now) for the >> final approval of prefix and the new EAPI3 [2]. You can also emerge >> =app-doc/pms-3 where EAPI3 and thus prefix is specified. It's a good >> time to start using this and send your comments to the prefix team >> about the available documentation. >> >> Denis. >> >> [1] http://www.gentoo.org/proj/en/council/meeting-logs/20091207-summary.txt >> [2] http://www.gentoo.org/proj/en/council/meeting-logs/20100118.txt > > Is there some guide around on "Porting ebuilds from EAPI=2 to EAPI=3 for > people who don't pay any attention to anything on mailing lists"? >
No there isn't. But for most ebuilds there is no big change to EAPI="2". Only exception are ebuilds using the python.eclass [1]. There you likely will have a lot of work and the chance is high that you hit a bug in the eclass. So I would recommend contacting Arfrever in any case of problems. He is really willing to help us. app-doc/pms includes the EAPI cheat paper from fauli. [1] http://dev.gentoo.org/~Arfrever/Guide_on_writing_ebuilds_supporting_installation_for_multiple_Python_versions
signature.asc
Description: OpenPGP digital signature
