Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 796245 - [Future EAPI] Allow calling EXPORT_FUNCTIONS with arbitrary/custom functions
Summary: [Future EAPI] Allow calling EXPORT_FUNCTIONS with arbitrary/custom functions
Status: CONFIRMED
Alias: None
Product: Gentoo Hosted Projects
Classification: Unclassified
Component: PMS/EAPI (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: PMS/EAPI
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: future-eapi
  Show dependency tree
 
Reported: 2021-06-15 18:16 UTC by Michał Górny
Modified: 2021-06-15 19:20 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2021-06-15 18:16:39 UTC
I don't think we really have any technical reason to restrict EXPORT_FUNCTIONS to the standard phase functions defined by EAPI.  The same aliasing behavior is sometimes useful for custom functions.  I can think of two examples:

1. 'Pseudo-phases' used e.g. by distutils-r1.eclass.  Right now the eclass explicitly aliases 'python_test() { distutils-r1_python_test; }'.  While it's not a big deal, I suppose it would be cleaner to use EXPORT_FUNCTIONS consistently for it.

2. Custom phase functions for internal use.  In particular, I'm working on moving smart-live-rebuild logic to a phase-like function.