On Sat, Aug 28, 2021 at 06:35:06PM +0200, Michał Górny wrote: > Hi, > > I've been informed of a slight inconsistency in package manager behavior > that affects combining EXPORT_FUNCTIONS with inherit (by ionic, thanks > for the report!). Please consider the three following snippets: ...
> 1. I'd like to propose that we explicitly require all inherits to happen > before EXPORT_FUNCTIONS. This will ensure consistent behavior across > all package managers. > > 2. I'd like to ask your opinion whether we should: > > a. revert the Portage behavior to be consistent with PkgCore/Paludis > > b. update PMS to identify the behavior as 'undefined', i.e. either > solution is correct. I would go with 1 and 2 b, but I also propose another option for the next eapi which may be a bit controversial. Starting with eapi 9, make export_functions a noop (you can't remove it until all eclasses/ebuilds only support eapis that don't require it). I understand that this is controversial, because it would require a lot of work to convert ebuilds to eapi 9, but it would eliminate this ambiguity/inconsistency in the future because it would require all ebuilds to have phase functions unless they can use the default phases the eapis provide. Thoughts? William > > WDYT? > > > [1] > https://github.com/gentoo/portage/commit/06d4433e8b8be60d606733b9e23f57f8a5869d8f > > -- > Best regards, > Michał Górny > > >
signature.asc
Description: PGP signature
