Summary: | [Future EAPI] query functions for ebuild-defined variables | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | Patrick McLean <chutzpah> |
Component: | PMS/EAPI | Assignee: | PMS/EAPI <pms> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | esigra |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 174380 |
Description
Patrick McLean
2019-12-05 22:56:32 UTC
Questions: 1. USE-conditional expressions in *DEPEND etc. should be evaluated, I suppose? 2. How would groups like "|| ( )" be handled? 3. How exactly should dependency specifications be matched? For example, if the ebuild has >=dev-python/setuptools-50.3.0 in *DEPEND, would dev-python/setuptools match (and vice versa)? 4. Should slot dependencies and USE dependencies be included in the matching? TBH, I'd rather see a proof-of-concept implementation before we consider this for the next EAPI. |