Summary: | emerge -b create files with strange filepaths in them | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Xake <kanelxake> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Xake
2010-05-03 19:02:44 UTC
This thing about ./ in the path seems like it might be a red herring. (In reply to comment #0) > >>> Checking ghc-6.10.4-src.tar.bz2's mtime... > >>> ghc-6.10.4-src.tar.bz2 has been updated; recreating WORKDIR... > >>> Unpacking source... Is this the mtime thing you're talking about? The portage code there is a little bit dumb, but there is a reason for it. I don't understand why you are trying to re-use the existing content of WORKDIR instead of doing a fresh unpack. Can you explain? (In reply to comment #1) > This thing about ./ in the path seems like it might be a red herring. > Yeah, I think so to > Is this the mtime thing you're talking about? The portage code there is a > little bit dumb, but there is a reason for it. I may understand it, but still I do think it is nice if portage does not break with files it self has created > I don't understand why you are > trying to re-use the existing content of WORKDIR instead of doing a fresh > unpack. Can you explain? > GHC has many problem on hardened, and I am trying to figure out why some stuff does not work like it should. I try to do this by issuing "ebuild compile", see what breaks, maybe make a small change to see how it reacts and then "ebuild compile" again. If workdir then is preserved you can pretty easily see if it broke more or actually is something to try make a patch out of. However if it behaves like for GHC (mind only with packages generated by "emerge -b", not by quickpkg) then you actually have to make the ebuild make those small changes every time, which is somewhat timeconsuming if you only are poking around trying to figure out why -nopie was not added in a command where it should be. *** This bug has been marked as a duplicate of bug 332217 *** |