| Summary: |
[TRACKER] Multilib dependencies need to be >= on min-ver(EAPI=5, supporting multilib) |
| Product: |
Gentoo Linux
|
Reporter: |
Michał Górny <mgorny> |
| Component: |
Current packages | Assignee: |
Multilib team <multilib+disabled> |
| Status: |
RESOLVED
FIXED
|
|
|
| Severity: |
normal
|
CC: |
bertrand, orionbelt2, sam
|
| Priority: |
Normal
|
Keywords: |
Tracker |
| Version: |
unspecified | |
|
| Hardware: |
All | |
|
| OS: |
Linux | |
|
| Whiteboard: |
|
|
Package list:
|
|
Runtime testing required:
|
---
|
|---|
| Bug Depends on: |
513770, 513772, 513774, 513776, 513778, 513780, 513782, 513784, 513786, 513788, 513790, 513792, 513794, 513796, 513798, 513800, 517442
|
|
|
| Bug Blocks: |
525256
|
|
|
EAPI magicians can probably tell you more but long story short, EAPI<5 ebuilds can randomly satisfy ${MULTILIB_USEDEP} deps. This results in two big issues: 1. random old ebuilds can pretend to be multilib when they're not, effectively breaking other multilib ebuilds, 2. repoman won't complain when you stabilize multilib ebuild with unstable deps, and then emerge will want to downgrade to EAPI<5 version to 'satisfy' deps on stable. Since so far there's no good solution for this, we've decided to go the hard way and require every multilib dependency to have >= operator and version matching either first ebuild of continuous EAPI=5 ebuilds or continuous multilib ebuilds. In other words, instead of: dev-foo/bar[${MULTILIB_USEDEP}] you use: >=dev-foo/bar-${BAR_PV}[${MULTILIB_USEDEP}] where ${BAR_PV} is chosen so that either: a) all ebuilds >= ${BAR_PV} are EAPI=5 or newer, b) all ebuilds >= ${BAR_PV} are multilib.