| Summary: | prefix-portage: Cross-prefix building doesn't work | ||
|---|---|---|---|
| Product: | Gentoo/Alt | Reporter: | Ruud Koolen (RETIRED) <redlizard> |
| Component: | Prefix Support | Assignee: | Gentoo Prefix <prefix> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | Keywords: | PATCH |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | portage-cross-prefix.patch | ||
Hmmm, will this break something else? I added it back then on purpose. Guess we need to run without it for a while to test and see if it doesn't break. (I got lost what should be where, unfortunately.) > Hmmm, will this break something else? It shouldn't. `mysettings` is a config object, which initializes a value of EPREFIX in its constructor (pym/portage/package/ebuild/config.py:489), and it is this value that should be used, not the constant one. > (I got lost what should be where, unfortunately.) I only have a vague idea myself, so by all means check my work. But in any case, const.EPREFIX is the wrong value to use here, the prefix to use can be overridden by settings. Pushed as 9e892c7 already resolved? Yes. |
Created attachment 368842 [details, diff] portage-cross-prefix.patch The functionality in portage to build packages cross-eprefix works in the mainline branch, but ironically doesn't work in prefix branch. Attached patch fixes it.