Summary: | automatic RDEPEND for binpkgs using python | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Victor Mataré <vmatare+gbug> |
Component: | Binary packages support | Assignee: | PMS/EAPI <pms> |
Status: | RESOLVED DUPLICATE | ||
Severity: | enhancement | CC: | darkside |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 192319 | ||
Bug Blocks: |
Description
Victor Mataré
2011-05-04 01:30:56 UTC
I'm not on the dev-portage team, but I consider it proper binhost maintenance to run the tools to rebuilds packages after major upgrades (eg. python-updater). I'll add myself to CC to listen. (In reply to comment #1) > I'm not on the dev-portage team, but I consider it proper binhost maintenance > to run the tools to rebuilds packages after major upgrades (eg. > python-updater). I'll add myself to CC to listen. The problem is not on the binhost. The use case I'm talking about is this: binhost updates python to 2.7, then builds pkg-xy with python:2.7 client has not yet upgraded to python:2.7 (only 2.6 available) and tries to emerge pkg-xy as binpkg. This fails because pkg-xy was built with python:2.7 which is not available. This requires some form of ABI dependency metadata, related to bug 192319. Note that this would Just Work(tm) if USE_PYTHON was done as a USE_EXPAND with appropriate conditional deps, similar to RUBY_TARGETS. *** This bug has been marked as a duplicate of bug 192319 *** |