Blag

He's not dead, he's resting

What’s in EAPI 3?

EAPI 3’s feature list has been provisionally approved by the Gentoo Council, subject to nothing going wrong when Portage implements it. It’s not yet usable in ebuilds.

EAPI 3 is defined based upon EAPI 2. The changes are:

Full and precise definitions will be provided in PMS (and can currently be found in a draft PMS branch); an overview of each feature will appear in subsequent posts.

Advertisements

13 responses to “What’s in EAPI 3?

  1. Pingback: EAPI 3: pkg_pretend « Ciaran McCreesh’s Blag

  2. Pingback: EAPI 3: Slot operator dependencies « Ciaran McCreesh’s Blag

  3. Pingback: EAPI 3: Use Dependency Defaults « Ciaran McCreesh’s Blag

  4. Pingback: EAPI 3: DEFINED_PHASES and PROPERTIES Mandatory « Ciaran McCreesh’s Blag

  5. Pingback: EAPI 3: default src_install « Ciaran McCreesh’s Blag

  6. Pingback: EAPI 3: dohard and dosed Banned « Ciaran McCreesh’s Blag

  7. Pingback: EAPI 3: unpack xz Support « Ciaran McCreesh’s Blag

  8. Pingback: EAPI 3: pkg_info Changes « Ciaran McCreesh’s Blag

  9. Pingback: EAPI 3: S to WORKDIR Fallback Reduced « Ciaran McCreesh’s Blag

  10. Pingback: EAPI 3: No More RDEPEND=DEPEND « Ciaran McCreesh’s Blag

  11. Pingback: EAPI 3: Utilities Die, and New nonfatal Utility « Ciaran McCreesh’s Blag

  12. Pingback: What’s Not in EAPI 3? « Ciaran McCreesh’s Blag

  13. Pingback: What’s Happened to EAPI 3? « Ciaran McCreesh’s Blag

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s