Summary: | Emerge behaves differently depending on package is in its own directory or in external portdir directory. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | G. Náray <g_naray> |
Component: | New packages | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
G. Náray
2009-12-19 12:49:55 UTC
(In reply to comment #0) > line 876: epatch: parancs nem található The ebuild was missing 'inherit eutils'. I've just fixed that. Why it's behaving differently is beyond me, so leaving this open for dev-portage@ My first guess is that your overlay overrides some eclasses from the main tree and those eclasses inherit eutils while the ones in the main tree do not. I know this bug will not be easy to find, and this is not even the toughest. First of all, i do not know much about eclass. It is similar to ebuild, but eclass is for including. That is ebuilds can use eclasses, right? My overlay directory is quite small, it contains app-emulation/winex-transgaming, distfiles (for transgaming), media-video/xanim, and layman (make.conf in layman is empty). The xanim directory contains xanim-2.80.1-r4.ebuild, xanim-2.80.1-r5.ebuild (it is my version for testing), Manifest, metadata.xml (copy of original), files/xanim-2.80.1-gcc41.patch (copy of original), files/xanim-2.80.1-gcc412.patch (my version for testing). Considering the files, i did not override any eclass, so the problem must be elsewhere. Next idea? If you use at least a recent version of portage-2.1.7.x then the --debug option will make it show a trace of the the eclass inheritance process and that should contain clues about how eutils.eclass got inherited (assuming inheritance of eutils.eclass is how the epatch function entered the ebuild enviroment). |